Re: JavaMemoryModel: Class initialization safety is hard

From: Joshua Bloch (
Date: Thu Jul 15 1999 - 03:34:20 EDT


   Sorry, I didn't get around to wading through your message till today:

> * This Class object is fully initialized and ready for use.
> is interpreted as "_This_ thread has a fully initialized view of the
> Class",

   I beieve that this is the correct interpretation!

>then we need lots of memory barriers and other complications
> on relaxed memory order systems.

    Life's a bitch.

> And, of course, there is the problem with virtual method invocations.
> If we don't add them to the list of things that are guaranteed an
> initialized class, then we also loose class initialization safety.

   Sounds like there may be a bug in the JVMS (though I haven't read it
closely enough to know for sure).

     Hopefully our game of phone tag will end tomorrow.


This is the JavaMemoryModel mailing list, managed by Majordomo 1.94.4.

To send a message to the list, email
To send a request to the list, email and put
your request in the body of the message (use the request "help" for help).
For more information, visit

This archive was generated by hypermail 2b29 : Thu Oct 13 2005 - 07:00:16 EDT