Precedence doesn't have an effect on order of evaluation (except as necessary - some sub-expressions might need to be evaluated before others due to precedence). For example, in the simple expression:
a() + b() + c() * d()
even though multiplication has precedence over addition, the compiler is free to perform the calls to the functions in any order it likes, and might call a()
or b()
before or after it performs the multiplication. Obviously, it does have to evaluate c()
and d()
before it performs the multiplication. If these functions have side-effects (like modifying and using global variables), the indeterminate evaluation order could result in unexpected outcomes.
However, for some operators, the standard does prescribe a strict order of evaluation. It this to say about the ||
logical or operator:
Unlike the bitwise | operator, the || operator guarantees left-to-right evaluation; there is
a sequence point after the evaluation of the first operand. If the first operand compares
unequal to 0, the second operand is not evaluated.
So not only does the ||
provide an ordering guarantee, it also guarantees that under certain conditions, the 2nd operand won't be evaluated at all.
(it also says something similar for the &&
- except that in that case the 2nd operand isn't evaluated if the first evaluates to 0. But in your example, the ||
comes first).
Other operators that provide some guarantee of ordering include the comma operator and the function call (which guarantees that arguments have been evaluated, but not the order in which those arguments have been evaluated).