561
edits
Difference between revisions of "Code Formatting Conventions"
Code Formatting Conventions (view source)
Revision as of 16:06, 4 October 2009
, 16:06, 4 October 2009→Naming: change "classes" naming section to general type nameing
(→Whitespaces: add section about references) |
(→Naming: change "classes" naming section to general type nameing) |
||
| Line 160: | Line 160: | ||
(As a side remark, we recommend avoiding #define for creating constants, because these can lead to weird and difficult to track down conflicts. Instead use enums or the <code>const</code> keyword.) | (As a side remark, we recommend avoiding #define for creating constants, because these can lead to weird and difficult to track down conflicts. Instead use enums or the <code>const</code> keyword.) | ||
''' | '''Type names''' | ||
Camel case starting with upper case. | Camel case starting with upper case. | ||
<syntax type="C++"> | <syntax type="C++"> | ||
class MeClass() { | class MeClass() { /* ... */ } | ||
struct MeStruct() { /* ... */ } | |||
typedef int MyInt; | |||
</syntax> | </syntax> | ||