Difference between revisions of "Documentation/4.0/Developers/Style Guide/Cpp"
(→Tools) |
|||
| Line 31: | Line 31: | ||
OK, enough writing about writing code; the code itself is much more interesting. Have fun! | OK, enough writing about writing code; the code itself is much more interesting. Have fun! | ||
| − | <i>Source: [https://google-styleguide.googlecode.com/svn/trunk/cppguide.xml | + | <i>Source: [https://google-styleguide.googlecode.com/svn/trunk/cppguide.xml Google C++ Style Guide]</i> |
}} | }} | ||
Revision as of 06:01, 3 November 2011
Home < Documentation < 4.0 < Developers < Style Guide < Cpp |
Page under construction. |
References
- https://secure.wikimedia.org/wikipedia/en/wiki/Indent_style#GNU_style
- https://google-styleguide.googlecode.com/svn/trunk/cppguide.xml
Tools
 |
Use common sense and BE CONSISTENT.
If you are editing code, take a few minutes to look at the code around you and determine its style. If they use spaces around their if clauses, you should, too. If their comments have little boxes of stars around them, make your comments have little boxes of stars around them too. The point of having style guidelines is to have a common vocabulary of coding so people can concentrate on what you are saying, rather than on how you are saying it. We present global style rules here so people know the vocabulary. But local style is also important. If code you add to a file looks drastically different from the existing code around it, the discontinuity throws readers out of their rhythm when they go to read it. Try to avoid this. OK, enough writing about writing code; the code itself is much more interesting. Have fun! Source: Google C++ Style Guide |
