From: terekhov (terekhov_at_[hidden])
Date: 2002-01-16 13:37:07
--- In boost_at_y..., "bill_kempf" <williamkempf_at_h...> wrote:
> --- In boost_at_y..., "terekhov" <terekhov_at_d...> wrote:
> > --- In boost_at_y..., "David Abrahams" <david.abrahams_at_r...> wrote:
> > > Do you feel that someone is failing to account for the
> > > experience of the pthreads committee? That would certainly be a
> > mistake, but
> > > I didn't notice it happening.
> > For example:
> > http://groups.google.com/groups?as_umsgid=3C33232D.EE55A880%
> > My problem is that under PTHREADS, a thread
> > reference/id value object (pthread_t) provided
> > by pthread_self() IS SHARABLE and I use this.
> > Boost.Threads, AFAIK, does not provide such
> > functionality, unfortunately.
> The link talks about a totally different subject from whether or
> this is shareable. A boost::thread object created with the default
> constructor (equivalent to a pthread_self()) is shareable in any
I mean *thread-*shareable:
Effects: Constructs a thread object representing the current thread
Postcondition: *this is non-joinable.
Danger: *this is valid only within the current thread"
> It's just not joinable. Do you actually call pthread_join()
> on references returned from pthread_self()? Why?
To let someone else join (compare/cancel/etc) the "current"
thread. For example, initial/main thread.
> I still may reconsider this decision.
ps. the other point I was trying to make in my posting
was that Boost.Thread thread objects are completely
different beasts from PTHREADS thread objects, just
do a search on "object" in e.g. Compaq PTHREADS-impl
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk