In Java, the body of a do-while
loop and the loop condition do not belong to the same scope. So the following code won't compile:
do {
boolean b = false;
} while (b); // b cannot be resolved to a variable
But this code does make sense to me.
Also, I cannot find any pitfalls if the body and the condition are in the same scope; since the body will always get executed, and Java does not have Goto
, I don't know how a variable declaration in the outermost do-while
body scope could be skipped. Even if it is possible, the compiler could always detect such possibility and then produce compile time errors.
Is there any reason for this behavior (aside from keeping the do-while
loop in the same format as while
)? I am really curious. Thanks for any inputs!
Because the boolean variable
b
is a local variable having scope only within a block.From the JLS:
The statement definition and your variable are not visible outside your statement block
{}
, which is why the compiler complains.The difference between the
while
anddo ... while
is that thedo ... while
is guaranteed to execute at least once and that is a more simpler way to write according to the JLSRegarding scope of a variable, it has to be visible, according to these rules or else you get a compile time error.