Re: finalize called on an object that's still in scope?
Tom Hawtin wrote:
Paul Tomblin wrote:
Ah, ok. I didn't realize that Java did that sort of optimization. I
still think in terms of scope rules. If I put a bogus use of the local
variable after the while(true) loop, that should prevent that, right?
It would have to be something that couldn't be optimised away. Trying to
guess the rules is hard.
Sure. Just trying to figure out what that rules might be, and how to
prevent against them, I've found the following:
...
while (true) {
try {
Thread.sleep(5000);
} catch (InterruptedException ie) {
if (ie.equals(lineup)) {
throw new AssertionError();
}
}
}
Do you think Tom, it is possible to optimize the above fragment in the
way that a lineup local is removed form a locals stack (i.e. becomes
unreachable) before a loop ends?
Anyway, Paul, consider also using another object to make a lineup
non-local for a "moment":
...
new Object() {
Object lineup_ = lineup; /* lineup must be final */
void loop() {
while (true) {
try {
Thread.sleep(5000);
} catch (InterruptedException ie) {
/* ignore */
}
}
}
}.loop();
piotr