David Holmes wrote,
> Miles Sabin wrote:
> > The conclusion I came to later was that interruption was
> > inadequate for reliable handling of cancellation because a
> > thread's interrupt status can be modified unpredictably, eg. _any_
> > holder of a reference to the thread running the cancellable activity
> > can set or clear the thread's interrupt status
>
> Nitpick. That's not quite true. Anyone with a reference and the right
> permission can set the interrupt state, but only the thread can clear
> its own interrupt state. This latter fact is important for adding
> sanity to the interruption process otherwise it would be completely
> unworkable.
True, but I was thinking specifically of cases where code from two or
more independently developed modules share a single thread ... not
particularly uncommon in my experience.
Cheers,
Miles
-------------------------------
JavaMemoryModel mailing list - http://www.cs.umd.edu/~pugh/java/memoryModel
This archive was generated by hypermail 2b29 : Thu Oct 13 2005 - 07:00:45 EDT