Re: [boost] [thread] Do we need thread_group now?

Subject: Re: [boost] [thread] Do we need thread_group now?
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2012-04-13 18:19:34

Vicente J. Botet wrote:
>
> now that we have Boost.Container and Boost.Thread (trunk)
> uses Boost.Move,  boost::thread_group has less sense.
>
> I was thinking on replacing it by some generic algorithms as
> join_all, interrupt_all that work with generic containers so
> that the user can use the best containers adapted to her own
> needs.
[snip]
> Could boost::thread_group be deprecated once these generic
> algorithm are released? Or, is there something really useful
> on the thread_group class that needs to be preserved or even
> improved?

I like your idea.  thread_group is an odd thing.  If you want access to the threads in the group, you must track the pointers in another container because you can't iterate a thread_group.  To remove a thread, you also must retain the pointer versus using its ID, for example.  thread_group is an odd container, so I'm in favor of supporting the group functionality using ordinary containers.

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer                     using std::disclaimer;
Dev Tools & Components
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.