Page History

...

Although it advises against depending on parentheses for specifying evaluation order, EXP05-J. Do not write more than once to the same variable within an expression applies only to expressions that contain side effects.

Noncompliant Code Example

The intent of the expression in this noncompliant code example is to add the variable OFFSET to the result of the bitwise logical AND between x and MASK:

...

x & (1337 - 1337)

Compliant Solution

This compliant solution uses parentheses to ensure that the expression is evaluated as intended:

public static final int MASK = 1337;
public static final int OFFSET = -1337;

public static int computeCode(int x) {
  return (x & MASK) + OFFSET;
}

Noncompliant Code Example

In this noncompliant code example, the intent is to append either "0" or "1" to the string "value=":

...

However, the precedence rules result in the expression to be printed being parsed as ("value=" + s) == null? 0 : 1.

Compliant Solution

This compliant solution uses parentheses to ensure that the expression evaluates as intended:

public class Test{
    public static void main(String[] args) {
        String s = null;
        System.out.println("value=" + (s == null? 0 : 1)); // Prints "value=0" as expected
    }
}

Applicability

Mistakes regarding precedence guidelines can cause an expression to be evaluated in an unintended way, which can lead to unexpected and abnormal program behavior.

...

Detection of all expressions using low-precedence operators without parentheses is straightforward. Determining the correctness of such uses is infeasible in the general case; heuristic warnings could be useful.

Bibliography

...