[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

Previous message: [concurrency-interest] Curious: How Java Memory Model is satisfied in JSR166 locks?
Next message: [concurrency-interest] Curious: How Java Memory Model is satisfied in JSR166 locks?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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

One word: volatile.

Previous message: [concurrency-interest] Curious: How Java Memory Model is satisfied in JSR166 locks?
Next message: [concurrency-interest] Curious: How Java Memory Model is satisfied in JSR166 locks?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Concurrency-interest mailing list