Noncompliant Code Example
Do not use the character sequence
/* within a comment:
In this example, the call to the security-critical function is not executed. A reviewer examining this page could incorrectly assume that the code is executed.
If execution failure is the result of an accidental omission, it is useful to use an editor that provides syntax highlighting or formats the code to help identify issues like missing end-comment delimiters.
Because missing end delimiters are error prone and often viewed as a mistake, this approach is not recommended for commenting out code.
Compliant Solution (Preprocessor)
Instead of using
*/ to comment out blocks of code, use conditional compilation (for example,
The text inside a block of code commented out using
#ifndef must still consist of valid preprocessing tokens. This means that the characters
' must each be paired just as in real C code, and the pairs must not cross line boundaries. In particular, an apostrophe within a contracted word looks like the beginning of a character constant. Consequently, natural-language comments and pseudocode should always be written between the comment delimiters
*/ or following
Compliant Solution (Compiler)
This compliant solution takes advantage of the compiler's ability to remove unreachable (dead) code. The code inside the
if block must remain acceptable to the compiler. If other parts of the program, such as macros, types, or function prototypes, later change in a way that would cause syntax errors, the unexecuted code must be brought up to date to correct the problem. Then, if it is needed again in the future, the programmer need only remove the surrounding
if statement and the
NOTREACHED comment tells some compilers and static analysis tools not to complain about this unreachable code. It also serves as documentation.
This code is an instance of exception MSC07-C-EX2 to MSC07-C. Detect and remove dead code.
Noncompliant Code Example
Following are some additional examples of comment styles that are confusing and should be avoided:
Use a consistent style of commenting:
Confusion over which instructions are executed and which are not can lead to serious programming errors and vulnerabilities, including denial of service, abnormal program termination, and data integrity violation. This problem is mitigated by the use of interactive development environments (IDEs) and editors that use fonts, colors, or other mechanisms to differentiate between comments and code. However, the problem can still manifest, for example, when reviewing source code printed on a black-and-white printer.
Can detect violations of this rule when the
|LDRA tool suite|
|119 S, 302 S, 611 S|
The character sequence /* shall not be used within a C-style comment
|Polyspace Bug Finder|
Language extensions should not be used
The character sequences
|SEI CERT C++ Coding Standard||VOID MSC04-CPP. Use comments consistently and in a readable fashion|
Rule 1.2 (advisory)