|
Boost : |
From: John Max Skaller (skaller_at_[hidden])
Date: 2001-06-26 17:30:53
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.
-- John (Max) Skaller, mailto:skaller_at_[hidden] 10/1 Toxteth Rd Glebe NSW 2037 Australia voice: 61-2-9660-0850 New generation programming language Felix http://felix.sourceforge.net Literate Programming tool Interscript http://Interscript.sourceforge.net
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk