Java Memory Model mailing list archive: RE: JavaMemoryModel: Mi (original) (raw)
RE: JavaMemoryModel: Minor issue on hb edges and interrupts
From: Bill Pugh (pugh@cs.umd.edu)
Date: Thu Mar 18 2004 - 08:08:21 EST
- Next message: Vijay Saraswat: "[Fwd: Re: JavaMemoryModel: Question about the semantics of volatile]"
- Previous message: Eliot Moss: "Re: JavaMemoryModel: allowed semantics question"
- Maybe in reply to: Bill Pugh: "JavaMemoryModel: Minor issue on hb edges and interrupts"
- Next in thread: Doug Lea: "RE: JavaMemoryModel: Minor issue on hb edges and interrupts"
- Reply: Doug Lea: "RE: JavaMemoryModel: Minor issue on hb edges and interrupts"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Mail actions: [ respond to this message ] [ mail a new topic ]
[Reposted msg from Hans]
Perhaps another way to think of it is that the "isInterrupted" flag is
used to communicate between threads. As such, we'd tell a programmer
that
it should be made volatile. Thus it would be counterintuitive if the
library didn't follow the same rules.
Hans
-------------------------------
JavaMemoryModel mailing list - http://www.cs.umd.edu/~pugh/java/memoryModel
- Next message: Vijay Saraswat: "[Fwd: Re: JavaMemoryModel: Question about the semantics of volatile]"
- Previous message: Eliot Moss: "Re: JavaMemoryModel: allowed semantics question"
- Maybe in reply to: Bill Pugh: "JavaMemoryModel: Minor issue on hb edges and interrupts"
- Next in thread: Doug Lea: "RE: JavaMemoryModel: Minor issue on hb edges and interrupts"
- Reply: Doug Lea: "RE: JavaMemoryModel: Minor issue on hb edges and interrupts"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Mail actions: [ respond to this message ] [ mail a new topic ]
This archive was generated by hypermail 2b29: Thu Oct 13 2005 - 07:01:00 EDT