>
>Well, in the spirit of sleaze^H^H^H^H^H^Hcompromise, how about:
>
> Every class that contains any final field is initialization safe
> (i.e., first-publication-safe).
> Others need not be.
>
>As mentioned before, there aren't any interesting cases where this
>doesn't have the right effect in practice. When any fields are
>mutable, programmers will need to lock anyway to eliminate conflicts.
Continuing in Doug's spirit...
Shouldn't this be that any final field is initalization safe, but
that other fields in the same class may not be?
Bill
-------------------------------
This is the JavaMemoryModel mailing list, managed by Majordomo 1.94.4.
To send a message to the list, email JavaMemoryModel@cs.umd.edu
To send a request to the list, email majordomo@cs.umd.edu and put
your request in the body of the message (use the request "help" for help).
For more information, visit http://www.cs.umd.edu/~pugh/java/memoryModel
This archive was generated by hypermail 2b29 : Thu Oct 13 2005 - 07:00:16 EDT