Re: [boost] [threads] wait() and signal() ?

Subject: Re: [boost] [threads] wait() and signal() ?
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2009-10-07 12:50:07

Roland Schwarz wrote:
> Gottlob Frege wrote:
> > If boost threads doesn't have a semaphore, we could add one.
>
> boost::thread doesn't have a semaphore for a purpose.
> boost::threads is modelled after the pthreads API, which does not
> need what you are seeking for. Perhaps you could look up a book
> on pthreads for an in depth explanation? For short in pthreads API the
> state and the notification are decoupled, which is a more general
> aproach.
>
> Of course you know it, but it is straight forward to get the
> equivalent of a semaphore with boost::threads.

Isn't it reasonable for a library to provide helpful, tested, reusable, and documented functionality?

I'm not arguing whether semaphores are an appropriate abstraction or whether their presence would encourage programming styles that should be discouraged.  Those are separate questions.  I'm merely arguing that eschewing a feature because it is fairly straightforward given the provided functionality is weak at best.

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer, Core Software      using std::disclaimer;
Susquehanna International Group, LLP  http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.