I want to know if the condition evaluation is executed in for
and while
loops in Java every time the loop cycle finishes.
Example:
int[] tenBig = new int[]{1,2,3,4,5,6,7,8,9,10};
for(int index = 0;index < tenBig.length;index++){
System.out.println("Value at index: "+tenBig[index]);
}
Will the index < tenBig.length
be execute every time the loop cycle finishes?
Assumption and experience tells me yes.
I know that in this example the tenBig.length
is a constant, so there won't be a performance impact.
But lets assume that the condition operation takes long in a different case.
I know the logical thing to do then is to assign the tenBig.length
to a variable.
Still I want to be sure that its evaluated every time.
Yes. Specifically, the condition part is executed before each loop body. So it's entirely possible that you never enter the body of the loop at all.
So taking your example:
This is the logical (not literal) equivalent:
Yes, it will logically evaluate the whole of the middle operand on every iteration of the loop. In cases where the JIT knows better, of course, it can do clever things (even potentially removing the array bounds check within the loop, based on the loop conditions).
Note that for types that the JIT doesn't know about, it may not be able to optimize specifically like this - but may still inline things like fetching the
size()
of anArrayList<T>
.Finally, I generally prefer the enhanced for loop for readability:
Of course, that's assuming you don't need the index for other reasons.
Short Answer: the condition is evaluated every time so:
WRONG:
CORRECT:
index < tenBig.length
will be execute before every time the loop cycle starts.It will print
"evaluated"
just before cycles starts. And one more time before loop finishes.Here are several bytecode compiling examples from the JVM spec.
As far as I know, the condition will be evaluated every time.
Regards.
It's going to be executed everytime the loop is entered, including the last evaluation which will yield index < length = false . Aside from this, even though the length of tenBig is const, the loop will always access this property so it would be ideal to assign it to a variable (even though it's not a reasonable speed gain in your example).