...
Tool | Version | Checker | Description | ||||||
---|---|---|---|---|---|---|---|---|---|
Compass/ROSE |
|
| Can detect simple violations of this rule. It needs to examine each expression and make sure that no variable is modified twice in the expression. Also no variable is modified once, and read elsewhere, with the single exception that a variable may appear on both the left and right of an assignment operator. | ||||||
Coverity Prevent | 5.0 | EVALUATION_ORDER | Can detect the specific instance where Statement contains multiple side-effects on the same value with an undefined evaluation order because with different compiler flags or different compilers or platforms, the statement may behave differently. | ||||||
| evalordrCP1.EXP30 | Fully implemented. | |||||||
GCC |
|
| Can detect violations of this rule when the | ||||||
Splint | 3.1.1 |
|
|
...
This rule appears in the C Secure Coding Standard as EXP30-C. Do not depend on order of evaluation between sequence pointsfor side-effects.
This rule appears in the Java Secure Coding Standard as EXP05-J. Do not write more than once to the same variable within an expression.
...