RE: JavaMemoryModel: More ordering constraints does not imply mor e reliable software

From: Miles Sabin (msabin@interx.com)
Date: Thu Jul 12 2001 - 02:59:04 EDT

David Holmes wrote,
> Hmmm - I guess I was thinking more of encapsulating the
> read/write/read sequence as a total barrier, rather than individual
> reads and writes. But you are right, such methods add very little
> when they are needed simply to complement the volatile actions that
> already exist in the code.

But surely "needed simply to complement the volatile actions that
already exist in the code" is the typical (only?) case.

Cheers,

Miles 

-- 
Miles Sabin                                     InterX
Internet Systems Architect                      27 Great West Road
+44 (0)20 8817 4030                             Middx, TW8 9AS, UK
msabin@interx.com                               http://www.interx.com/

-------------------------------
JavaMemoryModel mailing list - http://www.cs.umd.edu/~pugh/java/memoryModel

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