Comment by krylon

I am a little surprised that somebody wrote a blog post over this. Shouldn't it be obvious?

(Okay, as far as I remember, the volatile keyword in Java, when applied to primitive types, will cause access to those variables to be atomic. But then again, Java is not C/C++.)