Name | Checked | Synopsis |
---|
5.1.1.b
|
 |
Each source file shall start with a file header, for which the "file name", "description" and copyright notice are to be filled in. |
5.1.1.c
|
|
With respect to includes, each source file (.c and .h) shall be self-contained. |
5.1.1.d
|
|
Only files that are really needed shall be included. |
5.1.1.f
|
 |
With respect to user files, it is good practice to place the include of the header file with the own definitions of the source file at the top. |
5.1.1.1.b
|
 |
The content (body) of every header file shall be enclosed in #ifndef/#if !defined, #define and #endif. |
5.1.1.1.c
|
 |
Naming convention of the include guard of an include file named CCBB_foo.h is of format: CCBB_FOO_H |
5.1.1.2.b
|
 |
Each non-trivial function shall be accompanied by a doxygen style function header. |
5.1.2.b
|
|
Local variables shall not cause stack overflow. |
5.1.2.3.a
|
 |
Side effects shall not be relied upon between successive sequence points. |
5.1.2.3.b
|
 |
Expressions which mix operators from the set ">", ">=", "<", "<=", "==", "!=" with the binary operators from the set "<<", ">>", "^", "&", "|", "&&", "||" and which use two or more distinct operators from the latter set shall be fully parenthesized and shall not depend on the C precedence rules. |