Re: Volatile keyword

From:

Robert Klemme <shortcutter@googlemail.com>

Newsgroups:

comp.lang.java.programmer

Date:

Wed, 14 Dec 2011 22:35:03 +0100

Message-ID:

<9ksj4eFc7oU1@mid.individual.net>

On 14.12.2011 20:00, Patricia Shanahan wrote:

On 12/14/2011 10:39 AM, Robert Klemme wrote:

On 12/13/2011 08:54 AM, Peter Duniho wrote:

On 12/12/11 11:37 PM, Robert Klemme wrote:

[...]Bottom line is that the JVM spec does not make
any guarantees here (=A717.7 see Lew's reference).

I think it's worth being careful about "does not make any guarantees
here". The implication of 17.7 is that there _is_ in fact a guarantee=

for certain 64-bit fields marked as "volatile". Specifically, those
which are of the type "double" or "long". This is true even on 32-bit=

systems.

And what guarantee is there? Can you unambiguously formulate that and
provide reference to the JLS so everybody can check it?

As indicated in the quoted material, the relevant section is
"17.7 Non-atomic Treatment of double and long"
http://java.sun.com/docs/books/jls/third_edition/html/memory.html#61803=

Thank you Patricia and Daniel for helping my feeble eyes!

Kind regards

robert

--
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/