C programmers commonly make errors regarding the precedence rules of C operators because of the unintuitive low-precedence levels of
>>. Mistakes regarding precedence rules can be avoided by the suitable use of parentheses. Using parentheses defensively reduces errors and, if not taken to excess, makes the code more readable.
Subclause 6.5 of the C Standard defines the precedence of operation by the order of the subclauses.
Noncompliant Code Example
The intent of the expression in this noncompliant code example is to test the least significant bit of
x & 1 == 0
Because of operator precedence rules, the expression is parsed as
x & (1 == 0)
which evaluates to
(x & 0)
and then to
In this compliant solution, parentheses are used to ensure the expression evaluates as expected:
(x & 1) == 0
EXP00-C-EX1: Mathematical expressions that follow algebraic order do not require parentheses. For instance, in the expression
x + y * z
the multiplication is performed before the addition by mathematical convention. Consequently, parentheses to enforce the algebraic order would be redundant:
x + (y * z)
Mistakes regarding precedence rules may cause an expression to be evaluated in an unintended way, which can lead to unexpected and abnormal program behavior.
|Axivion Bauhaus Suite|
C3389, C3390, C3391, C3392, C3393, C3394, C3395, C3396, C3397, C3398, C3399, C3400
|LDRA tool suite|
361 S, 49 S
Use parenthesis to clarify expression order if operators with precedence lower than arithmetic are used
|Polyspace Bug Finder|
Checks for possible unintended evaluation of expression because of operator precedence rules (rec. fully covered)
|V502, V593, V634, V648|
|SonarQube C/C++ Plugin|
Search for vulnerabilities resulting from the violation of this rule on the CERT website.
|SEI CERT C++ Coding Standard||VOID EXP00-CPP. Use parentheses for precedence of operation|
|ISO/IEC TR 24772:2013||Operator Precedence/Order of Evaluation [JCW]|
|MISRA C:2012||Rule 12.1 (advisory)|
|[Dowd 2006]||Chapter 6, "C Language Issues" ("Precedence," pp. 287–288)|
|[NASA-GB-1740.13]||Section 6.4.3, "C Language"|
Good rule of thumb: if you have to look at an operator precedence chart to *write* your code, then so will your reader; add parens if there is any doubt.
Sound advice indeed.
Is the assignment operator (especially in conditions) addressed separately?
Yes, in MSC02-A.
added exception for standard algebraic precedence.