Re: [boost] Re: Boost.Threads - thread_desc concept

From: Greg Colvin (gcolvin_at_[hidden])
Date: 2001-06-26 18:36:32

From: John Max Skaller <skaller_at_[hidden]>
> williamkempf_at_[hidden] wrote:
> > 
> > 
> > The first impediment is that it's a very common practice to copy
> > the "thread" (actually the descriptor, as you pointed out) in order
> > to allow some other piece of the program manage the thread.  For
> > instance, a thread pool is going to have to store the threads in some
> > sort of data structure.  This design requires all such uses to be
> > dynamically allocated via new, which complicates the management
> > though it can be lessened by immediately placing them in a smart
> > pointer.
> 
> I'd say that simplifies the design by factoring the
> management and owenership of the thread object out, and leaving
> the thread object to just deal with thread related things.

I think I like it, but I'm not seeing an easy way to
create a thread object that goes away when the thread
exits.