Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Parenthesize all parameter names in macro definitions. See also PRE00-C. Prefer inline or static functions to function-like macros and PRE02-C. Macro replacement lists should be parenthesized.

...

Noncompliant Code Example

This CUBE() macro definition is noncompliant because it fails to parenthesize the parameter names.:

Code Block
bgColor#FFcccc
langc

#define CUBE(I) (I * I * I)

As a result, the invocation

Code Block
bgColor#FFcccc
langc

int a = 81 / CUBE(2 + 1);

expands to

Code Block
bgColor#FFcccc
langc

int a = 81 / (2 + 1 * 2 + 1 * 2 + 1);  /* evaluatesEvaluates to 11 */

which is clearly not the desired result.

Compliant Solution

Parenthesizing all parameter names in the CUBE() macro allows it to expand correctly (when invoked in this manner).:

Code Block
bgColor#ccccff
langc

#define CUBE(I) ( (I) * (I) * (I) )
int a = 81 / CUBE(2 + 1);

Exceptions

PRE01-C-EX1: When the parameter names are surrounded by commas in the replacement text, regardless of how complicated the actual arguments are, there is no need for parenthesizing the macro parameters. Because commas have lower precedence than any other operator, there is no chance of the actual arguments being parsed in a surprising way. Comma separators, which separate arguments in a function call, also have lower precedence than other operators, although they are technically different than from comma operators.

Code Block

#define FOO(a, b, c) bar(a, b, c)
/* ... */
FOO(arg1, arg2, arg3);

PRE01-C-EX2: Macro parameters cannot be individually parenthesized when concatenating tokens using the ## operator, converting macro parameters to strings using the # operator, or concatenating adjacent string literals. The following JOIN() macro below concatenates both arguments to form a new token. The SHOW() macro converts the single argument into a string literal, which is then concatenated with the adjacent string literal to form the format specification in the call to printf()passed as a parameter to printf() and as a string and as a parameter to the %d specifier. For example, if SHOW() is invoked as SHOW(66);, the macro would be expanded to printf("66" " = %d\n", 66);.

Code Block

#define JOIN(a, b) (a ## b)
#define SHOW(a) printf(#a " = %d\n", a)

See PRE05-C. Understand macro replacement when concatenating tokens or performing stringification for more information on using the ## operator to concatenate tokens.

Risk Assessment

Failing to parenthesize the parameter names in a macro can result in unintended program behavior.

Recommendation

Severity

Likelihood

Remediation Cost

Priority

Level

PRE01-C

medium

Medium

probable

Probable

low

Low

P12

L1

Automated Detection

...

ToolVersionCheckerDescription
Astrée
Include Page
Astrée_V
Astrée_V
macro-parameter-parenthesesFully checked
Axivion Bauhaus Suite

Include Page
Axivion Bauhaus Suite_V
Axivion Bauhaus Suite_V

CertC-PRE01Fully implemented
ECLAIR
Include Page
ECLAIR_V
ECLAIR_V
CC2.PRE01Fully implemented
Helix QAC

Include Page
Helix QAC_V
Helix QAC_V

C3410
Klocwork
Include Page
Klocwork_V
Klocwork_V
MISRA.DEFINE.NOPARS
LDRA tool suite
Include Page
LDRA_V
LDRA_V

78 S

Enhanced Enforcement

Parasoft C/C++test
Include Page
Parasoft_V
Parasoft_V
CERT_C-PRE01-a
In the definition of a function-like macro each instance of a parameter shall be enclosed in parentheses unless it is used as the operand of # or ##
PC-lint Plus

Include Page
PC-lint Plus_V
PC-lint Plus_V

9022

Fully supported

Polyspace Bug Finder

Include Page
Polyspace Bug Finder_V
Polyspace Bug Finder_V

CERT C: Rec. PRE01-CChecks for expanded macro parameters not enclosed in parentheses (rule partially supported)


PVS-Studio

Include Page
PVS-Studio_V
PVS-Studio_V

V733
RuleChecker
Include Page
RuleChecker_V
RuleChecker_V
macro-parameter-parenthesesFully checked

The LDRA tool suite V 7.6.0 can detect violations of this recommendation.

Related Vulnerabilities

Search for vulnerabilities resulting from the violation of this rule on the CERT website.

References

Wiki Markup
\[[ISO/IEC 9899:1999|AA. C References#ISO/IEC 9899-1999]\] Section 6.10, "Preprocessing directives," and Section 5.1.1, "Translation environment"
\[[ISO/IEC PDTR 24772|AA. C References#ISO/IEC PDTR 24772]\] "JCW Operator precedence/Order of Evaluation"
\[[MISRA 04|AA. C References#MISRA 04]\] Rule 19.1
\[[Plum 85|AA. C References#Plum 85]\]
\[[Summit 05|AA. C References#Summit 05]\] Question 10.1

Related Guidelines

SEI CERT C++ Coding StandardVOID PRE01-CPP. Use parentheses within macros around parameter names
ISO/IEC TR 24772:2013Operator Precedence/Order of Evaluation [JCW]
Pre-processor Directives [NMP]
MISRA C:2012

Rule 20.7 (required)

Bibliography

[Plum 1985]
[Summit 2005]Question 10.1


...

Image Added Image Added PRE00-C      Edit       Image Modified