[concurrency-interest] Curious: How Java Memory Model is satisfied in JSR166 locks?

Matthias Ernst matthias at mernst.org
Tue Aug 21 08:46:43 EDT 2007


> I'm just curious that how lock implementations of JSR166 correctly
> satisfied the following requirement in the lock specification:

One word: volatile.


More information about the Concurrency-interest mailing list