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
Trailing whitespace #3
Comments
Agreed. Trailing whitespaces is also not allowed in the Google C++ Style Guide : http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml |
I am ready to go and fix whitespace issue in all the files. This means:
Since indentation style is also largely inconsistent, I would propose to make it a rule to use space-based indentation. What is your opinion about that? |
I would prefer space-based indentation. The Google C++ Style guide uses 2 spaces per indentation level, which I think is better than the 4 used by the Linux Kernel code guidelines. |
I prefer 4 spaces: screens nowadays are big, and it's easier to read with larger indentation. |
4 spaces makes it hard to keep the lines to 80 columns, which I got used to at Google, and is in the Google C++ Style Guide. But this is a religious war and I don't care either, as long as it's consistent. |
What about 3? :) |
Hi everyone, I don't have a strong opinion about 4 versus 2 spaces. If I had to choose foo to foo { On 13-07-09 11:09 AM, Jakob Leben wrote:
This message has been scanned for viruses and |
Whitespace has been fixed. |
Trailing whitespace are a real issue in this project. Nearly every file contains
trailing whitespace, which make it almost impossible to use
git add -p
or just view a diff if your editor is configured to strip whitespace automatically.
This project should follow the example of the the Linux code guidelines
and everybody working on this project should use an editor which strips
trailing whitespaces to reduce noise in git and possibly other CVS in the future.
The text was updated successfully, but these errors were encountered: