TrustedUser
574
edits
Difference between revisions of "Code Formatting Conventions"
Jump to navigation
Jump to search
Code Formatting Conventions (view source)
Revision as of 23:26, 20 February 2011
, 23:26, 20 February 2011→Switch / Case constructs: Added best practice to comment on fallthrough.
m (→Automatically converting code to our conventions: Update astyle config.) |
(→Switch / Case constructs: Added best practice to comment on fallthrough.) |
||
| Line 149: | Line 149: | ||
<syntax type="C++"> | <syntax type="C++"> | ||
switch (cmd) { | switch (cmd) { | ||
case kSomeCmd: | |||
SomeCmd(); | |||
// Fallthrough intended | |||
case kSomeVerySimilarCmd: | |||
SomeMoreCmd(); | |||
break; | |||
case kSaveCmd: | case kSaveCmd: | ||
save(); | save(); | ||
| Line 160: | Line 166: | ||
} | } | ||
</syntax> | </syntax> | ||
* Note comment on whether fallthrough is intentional. | |||
== Naming == | == Naming == | ||