If parenthesis has a higher precedence then why is increment operator solved first?
Expressions are evaluated left to right. Parentheses (and precedence) just express grouping, they don't express ordering of evaluation.
So
11 * (12 + 5)
++a ++a
equals
187
Quoting from Eric Lippert's Blog:
The evaluation of an arithmetical expression is controlled by three sets of rules: precedence rules, associativity rules, and order rules.
Precedence rules describe how an underparenthesized expression should be parenthesized when the expression mixes different kinds of operators.
Associativity rules describe how an underparenthesized expression should be parenthesized when the expression has a bunch of the same kind of operator.
Order of evaluation rules describe the order in which each operand in an expression is evaluated.
Higher precedence results in grouping of operands with an operator and doesn't mean the evaluation of operands. It is the order of evaluation which decides sequence of evaluation of sub-expressions in an expression.
Update:
As I can see many programmers think that statement
a = ++a * ( ++a + 5);
will invoke undefined behavior. Yes it will invoke UB if there is no guarantee of evaluation order of operands of an operator.
But this is not true in context of java programming language. It has well defined behavior in java (as well as in C#). The Java Language Specification states that:
15.7. Evaluation Order
The Java programming language guarantees that the operands of operators appear to be evaluated in a specific evaluation order, namely, from left to right.
Example 15.7.1-1. Left-Hand Operand Is Evaluated First
In the following program, the
*
operator has a left-hand operand that contains an assignment to a variable and a right-hand operand that contains a reference to the same variable. The value produced by the reference will reflect the fact that the assignment occurred first.class Test1 { public static void main(String[] args) { int i = 2; int j = (i=3) * i; System.out.println(j); } }
This program produces the output:
9
It is not permitted for evaluation of the
*
operator to produce 6 instead of 9.
But, still java specification clearly states that not to write such codes:
It is recommended that code not rely crucially on this specification. Code is usually clearer when each expression contains at most one side effect, as its outermost operation, and when code does not depend on exactly which exception arises as a consequence of the left-to-right evaluation of expressions.
From that snippet
int a = 10;
a = ++a * ( ++a + 5);
Sometimes, the most simple solution is to use javap to understand the evaluation order:
0: bipush 10 // push 10 onto the stack (stack={10})
2: istore_1 // store 10 into variable 1 (a = 10, stack={})
3: iinc 1, 1 // increment local variable 1 by 1 (a = 11, stack={})
6: iload_1 // push integer in local variable 1 onto the stack (a = 11, stack = {11})
7: iinc 1, 1 // increment local variable 1 by 1 (a = 12, stack={11})
10: iload_1 // push integer in local variable 1 onto the stack (a = 12, stack = {12, 11})
11: iconst_5 // load the int value 5 onto the stack (a = 12, stack = {5, 12, 11})
12: iadd // add 5 and 12 (a = 12, stack = {17, 11})
13: imul // multiply 17 and 11 (a = 12, stack = {})
a
is incremented by 1. (line 3) // a = 11a
is incremented by 1. (line 7) // a = 12- add
5
toa
(line 12) // a = 17 - multiply
11
to17
(line 13) // a = 187
(10 + 1 + 1 + 5) * 11 = 187