-
Notifications
You must be signed in to change notification settings - Fork 13.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cpplint can't handle multi word access specifiers (e.g., public slots:) correctly #30
Labels
Comments
tkruse
added a commit
to tkruse/cpplint
that referenced
this issue
Apr 23, 2016
based on google/styleguide#30 original patch by [email protected] Source code: class X : public QObject { ... public slots: ... } causes incorrectly message "Weird number of spaces at line-start. Are you using a 2-space indent? [whitespace/indent] [3]". Signed-off-by: Thibault Kruse <[email protected]>
tkruse
added a commit
to tkruse/cpplint
that referenced
this issue
Apr 23, 2016
based on google/styleguide#30 original patch by [email protected] Source code: class X : public QObject { ... public slots: ... } causes incorrectly message "Weird number of spaces at line-start. Are you using a 2-space indent? [whitespace/indent] [3]". Signed-off-by: Thibault Kruse <[email protected]>
tkruse
added a commit
to tkruse/cpplint
that referenced
this issue
Apr 23, 2016
based on google/styleguide#30 original patch by [email protected] Source code: class X : public QObject { ... public slots: ... } causes incorrectly message "Weird number of spaces at line-start. Are you using a 2-space indent? [whitespace/indent] [3]". Signed-off-by: Thibault Kruse <[email protected]>
tkruse
added a commit
to tkruse/cpplint
that referenced
this issue
Apr 23, 2016
based on google/styleguide#30 original patch by [email protected] Source code: class X : public QObject { ... public slots: ... } causes incorrectly message "Weird number of spaces at line-start. Are you using a 2-space indent? [whitespace/indent] [3]". Signed-off-by: Thibault Kruse <[email protected]>
tkruse
added a commit
to tkruse/cpplint
that referenced
this issue
Apr 23, 2016
based on google/styleguide#30 original patch by [email protected] Source code: class X : public QObject { ... public slots: ... } causes incorrectly message "Weird number of spaces at line-start. Are you using a 2-space indent? [whitespace/indent] [3]". Signed-off-by: Thibault Kruse <[email protected]>
tkruse
added a commit
to tkruse/cpplint
that referenced
this issue
Apr 24, 2016
based on google/styleguide#30 original patch by [email protected] Source code: class X : public QObject { ... public slots: ... } causes incorrectly message "Weird number of spaces at line-start. Are you using a 2-space indent? [whitespace/indent] [3]". Signed-off-by: Thibault Kruse <[email protected]>
tkruse
pushed a commit
to tkruse/cpplint
that referenced
this issue
Apr 24, 2016
based on google/styleguide#30 original patch by [email protected] Source code: class X : public QObject { ... public slots: ... } causes incorrectly message "Weird number of spaces at line-start. Are you using a 2-space indent? [whitespace/indent] [3]".
tkruse
pushed a commit
to tkruse/cpplint
that referenced
this issue
Apr 24, 2016
based on google/styleguide#30 original patch by [email protected] Source code: class X : public QObject { ... public slots: ... } causes incorrectly message "Weird number of spaces at line-start. Are you using a 2-space indent? [whitespace/indent] [3]".
tkruse
pushed a commit
to tkruse/styleguide
that referenced
this issue
May 13, 2016
based on google#30 original patch by [email protected] Source code: class X : public QObject { ... public slots: ... } causes incorrectly message "Weird number of spaces at line-start. Are you using a 2-space indent? [whitespace/indent] [3]".
public cpplint development in this repository has been halted (see #837). please migrate to https://github.com/cpplint/cpplint now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Original issue reported on code.google.com by
[email protected]
on 1 Oct 2014 at 9:09Attachments:
The text was updated successfully, but these errors were encountered: