Page History

Could detect violations of this recommendation by searching for the following pattern:

• • Any expression that calls two functions between the same sequence points
  • Those two functions both modify the value of a static variable
  • That static variable's value is referenced by code following the expression

Coverity

EVALUATION_ORDER

Can detect the specific instance where a statement contains multiple side effects on the same value with an undefined evaluation order because the statement may behave differently with different compiler flags or different compilers or platforms

Fully implemented

CERT_C-EXP10-a
CERT_C-EXP10-b
CERT_C-EXP10-c
CERT_C-EXP10-d

The value of an expression shall be the same under any order of evaluation that the standard permits
Don't write code that depends on the order of evaluation of function arguments
Don't write code that depends on the order of evaluation of function designator and function arguments
Don't write code that depends on the order of evaluation of expression that involves a function call

Checks for situations where expression value depends on order of evaluation or side effects (rec. fully covered)The value of an expression and its persistent side effects shall be the same under all permitted evaluation orders

0400 [U], 0401 [U],

0402 [U], 0403 [U],

0404 [U], 0405 [U],

3226, 3326