RE: JavaMemoryModel: A different slant with reference leakage

From: Sylvia Else (
Date: Mon Jan 19 2004 - 01:33:32 EST

At 04:45 PM 19/01/2004, David Holmes wrote:
> But the basic "rule"
>that tells the programmer they may have a problem is quite simple: in
>the absence of synchronization a variable read may return any value
>that it has ever held in the program. That's stating it worse than it
>is, because for any given read the memory model may reduce the set of
>possible return values.

However, this begs that question "what values has the variable held?" The
causality test cases show that the answers to this question can be unexpected.


JavaMemoryModel mailing list -

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