Re: [boost] Re: Redesigned thread class

From: Peter Dimov (pdimov_at_[hidden])
Date: 2001-08-30 07:16:55

From: "William Kempf" <williamkempf_at_[hidden]>
> From: "Peter Dimov" <pdimov_at_[hidden]>
> >From: "William Kempf" <williamkempf_at_[hidden]>
> >>From: "Peter Dimov" <pdimov_at_[hidden]>
> >> >5. current() cannot be used to adopts threads.
> >>
> >>Which is simply something that users won't accept.
> >
> >What do you base this statement on?
>
> Experience with other thread wrapper libraries.  Nothing that can be
proved,
> at least until you make this decision and get all of the complaints,
but....

Let's just say that I don't share your pessimism.

> >What can users do with an adopted thread?
>
> Currently, very little (as in comparing them to other thread objects is
it).
>   In the future there may be plenty, though, such as changing the thread's
> priority, possibly cancelling the thread (implementation defined), etc.

How can you cancel an adopted thread (from another thread)? The thread
object is not valid outside the adopted thread so you can't call .cancel()
on it. ;-)

--
Peter Dimov
Multi Media Ltd.