This already works as has been said by Denys.
There are two things, a first-class reference to a thread obtained by
Thread.this. They are unique, of course.
Then there is something obtained by Thread.id. Completely different story,
not unique, 16bit wrap-around integer-value.
Christian
"Konstantin Popov" <kost@sics.se> wrote in message
news:200305130730.h4D7U3s04239@sinuhe.sics.se...
>
> > > > - Unique thread ids: the book will assume that {Thread.this} returns
> > > > unique ids.
> > >
> > > I don't know what you mean by id. It returns a unique thread value.
> >
> > Is it truly unique? I thought that it was just a 16-bit value used to
> > help the debugger. If it's unique, then all's well. The book uses it
> > to define reentrant locking, and that only works if it is unique.
> a proper fix is under way (as a part of work by Dragan on mobile
> threads).
>
> Cheers,
>
> --- Kostja.
> -
> Please send submissions to hackers@mozart-oz.org
> and administriva mail to hackers-request@mozart-oz.org.
> The Mozart Oz web site is at http://www.mozart-oz.org/.
-
Please send submissions to hackers@mozart-oz.org
and administriva mail to hackers-request@mozart-oz.org.
The Mozart Oz web site is at http://www.mozart-oz.org/.