Miles Sabin wrote:
> I don't think you can have it both ways. Either dummy
> reads/writes are a viable and comprehensible technique, in which case
> {read,write}Barrier() would be even more so; or {read,write}Barrier()
> is not a viable and comprehensible technique, in which case dummy
> reads/writes aren't either (and maybe volatile accesses should be
> full two way barriers).
I totally agree - so please don't change your mind Miles :)
If "tricky" situations will require dummay accesses then lets not have
everyone reinvent the wrong trick for fixing things. Having some codified
helper classes/methods has got to be better than ad-hoc solutions being
rewritten over and over.
David Holmes
-------------------------------
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