On Thu, 07 Jun 2012 02:24:35 +0200, Cezary Biernacki <cezary...@gmail.com> wrote:
"* The semantics of volatile variables have been strengthened to have acquire and release semantics. In the original speciļ¬cation, accesses to volatile and non-volatile variables could be freely ordered.
Aha, so does this mean that "volatile" introduces the same memory semantics that a read lock does? If message is declared volatile, even its non-final fields would be guaranteed to be published properly? But if it's not volatile we have the usual problem with uninitialized fields? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
