Difference between revisions of "Cpp Coding Standards/FORMAT"
From Apache OpenOffice Wiki
m |
B michaelsen (Talk | contribs) (Code Format (FORMAT) , added newlines) |
||
| Line 4: | Line 4: | ||
===== Newline at End of File <span id="Eof">(Eof)</span> ===== | ===== Newline at End of File <span id="Eof">(Eof)</span> ===== | ||
Always conclude your source file with a newline character. [[/Eof|-> Details]] | Always conclude your source file with a newline character. [[/Eof|-> Details]] | ||
| + | |||
| + | ===== Unix-style Newlines <span id="Newlines">(Newlines)</span> ===== | ||
| + | Always use unix-style (NL, not CR NL) newlines. [[/Newlines|-> Details]] | ||
===== Source Code Character Set <span id="CharSet">(CharSet)</span> ===== | ===== Source Code Character Set <span id="CharSet">(CharSet)</span> ===== | ||
Latest revision as of 15:26, 10 December 2008
Contents
Code Format (FORMAT)
Generally, how to format the code does not need to be be governed by rules. Here are only a few things necessary for correct compiler behaviour or to increase code readability significantly.
Newline at End of File (Eof)
Always conclude your source file with a newline character. -> Details
Unix-style Newlines (Newlines)
Always use unix-style (NL, not CR NL) newlines. -> Details
Source Code Character Set (CharSet)
Don't use non-ASCII characters.
Exception: Use UTF8 encoding in resource files.
-> Details
No Cpp Comments in C Code (CppComm)
Don't use C++ comments in C code or C headers. -> Details
Indentation (Indent)
Indentation is 4 spaces. -> Details
No Tabs (NoTabs)
Use spaces, not tabs. -> Details
