12
edits
Difference between revisions of "Code Formatting Conventions"
Jump to navigation
Jump to search
Code Formatting Conventions (view source)
Revision as of 19:25, 28 March 2018
, 19:25, 28 March 2018Update fallthrough comment in switch example
(→Whitespaces: -- use proper C++ for Vertical alignment example) |
(Update fallthrough comment in switch example) |
||
| Line 166: | Line 166: | ||
case kSomeCmd: | case kSomeCmd: | ||
someCmd(); | someCmd(); | ||
// | // fall through | ||
case kSomeVerySimilarCmd: | case kSomeVerySimilarCmd: | ||
someMoreCmd(); | someMoreCmd(); | ||
| Line 181: | Line 181: | ||
} | } | ||
</source> | </source> | ||
* Note comment on whether fall through is intentional. | * Note comment on whether fall through is intentional. Use exactly this and not some variation both for consistency and so that the compiler will see it and suppress potential warnings. | ||
== Naming == | == Naming == | ||