Re: Boost.Threads - thread_desc concept

From: williamkempf_at_[hidden]
Date: 2001-06-27 08:45:37

--- In boost_at_y..., John Max Skaller <skaller_at_o...> wrote:
> williamkempf_at_h... 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.

It simplifies the design of the thread class, but it complicates the 
design of all code that uses it.  That's usually a bad trade off, 
IMHO.

Bill Kempf