...
Using reserved identifiers can lead to incorrect program operation.
Rule | Severity | Likelihood | Remediation Cost | Priority | Level |
|---|---|---|---|---|---|
DCL51-CPP | Low | Unlikely | Low | P3 | L3 |
Automated Detection
Tool | Version | Checker | Description | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Clang |
| -Wreserved-id-macro-Wuser-defined-literals | The -Wreserved-id-macro flag is not enabled by default or with -Wall, but is enabled with -Weverything. This flag does notcatch all instances of this rule, such as redefining reserved names. | ||||||
| CodeSonar |
| LANG.ID.NU.MK LANG.STRUCT.DECL.RESERVED | Macro name is C keyword Declaration of reserved name | ||||||
| LDRA tool suite |
| 86 S, 218 S, 219 S, 580 S | Fully implemented | ||||||
| Parasoft C/C++test |
|
|
| MISRA2008-17_0_1_ |
| a, |
| MISRA2008-17_0_1_b | Implemented |
| SonarQube C/C++ Plugin |
|
| 978 | ||||||||
| PRQA QA-C++ |
| 5003 |
Related Vulnerabilities
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
Related Guidelines
Bibliography
| [ISO/IEC 14882-2014] | Subclause 17.6.4.3, "Reserved Names" |
| [ISO/IEC 9899:2011 ] | Subclause 7.1.3, "Reserved Identifiers" |
...
...