C++ Coding Standard Specification - CERN

C++ Coding Standard
Specification
3 Coding Version/Issue: 1.1/5
CF4
All if statements should have an else clause.
This makes code much more readable and reliable, by clearly showing the flow paths.
The addition of a final else is particularly important in the case where you have
if/else-if.
Example:
if (val==ThresholdMin) {
statement;
} else if (val==ThresholdMax) {
statement;
} else {
statement; // handles all other (unforseen)cases
}
CF5
Do not use goto.
Use break or continue instead.
This statement remains valid also in the case of nested loops, where the use of control
variables can easily allow to break the loop, without using goto.
Source
Status
CXX-67, 9. GC, 24. RC
Common
CF6
Do not have overly complex functions.
The number of possible paths through a function, which depends on the number of control
flow primitives, is the main source of function complexity. Therefore you should be aware
that heavy use of control flow primitives will make your code more difficult to maintain.
As a rule of thumb, remember the 7±2 rule: typically methods should not be longer than 7±2
statements.
3.3 Object Life Cycle
In this paragraph it is suggested how objects are best declared, created, initialized, copied,
assigned and destroyed.
3.3.1 Initialization of Variables and Constants
CL1
Declare variables initialised to numeric values or strings in a highly visible position; whenever
possible collected them in one place.
It would be very hard to maintain a code in which numeric values or strings are spread over a
big file. If declaration and initialization of variable to numeric values or strings is put on the
most visible position, it will be easy to locate them, and maintain.
page 16
FINAL