Re: boost.threads [was RE: [boost] Re: sockets /network programming Requirements]

From: John Max Skaller (skaller_at_[hidden])
Date: 2001-08-05 15:03:17

williamkempf_at_[hidden] wrote:
> > > I want the main thread to be able to find out if
> > > any of the created threads have died.
> >
> >       This sounds like a possible design error.
> 
> That's the first reaction any competent MT programmer should have.
> The second reaction should also be to wonder if he's not dealing with
> a valid, though unusual, design.  There are corner cases where such
> designs are the most elegant solution to a problem, even if there
> exist other, more complicated, solutions.

        Yes. For example, the main thread loops, strobing
a red warning light until all worker threads have certainly died:
the requirement is that the warning light eventually go out
when the device door can be opened. 

> That said, I believe the reasons for such designs are unusual enough
> that it would be a mistake to account for them in the library.

        Lets say 'not yet'. I'd say we need to get a simple
design with a robust implementation first, before considering
extensions. 

        [I'd even be worried about 'once' stuff: this seems
like the moral equivalent of 'singletons' which I believe
are also often symptomatic of a design error: is there a 
compelling example for it 'once' 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