From: Michael Glassford (glassfordm_at_[hidden])
Date: 2004-02-16 12:03:09
Sergey Kurdakov wrote:
> Hello, sorry for slight OT but as for now there is a discussion which is entittled future of threads
>
> I wonder why those additions( which were mentioned here http://www.cuj.com/documents/s=8470/cuj0205kempf/
>
> There will be a boost::read_write_mutex, which will allow multiple threads to read from the shared resource at the same time, but
> will ensure exclusive access to any threads writing to the shared resource. There will also be a boost::thread_barrier, which will
> make a set of threads wait until all threads have "entered" the barrier. A boost::thread_pool is also planned to allow for short
> routines to be executed asynchronously without the need to create or destroy a thread each time.
>
> ) are stilll not in the main tree?
The reason is that William Kempf, the Boost.Thread maintainer and the
author of the article you link to above, apparently stopped active
development of Boost.Thread. There was previous discussion about this
not long ago in this newsgroup.
> not finished patches ( have some shortcomings )are here
>
> http://groups.yahoo.com/group/boost/files/thread_pool.zip
> http://groups.yahoo.com/group/boost/files/thread_barrier_v2.zip
> http://groups.yahoo.com/group/boost/files/thread_rw_lock_v2.zip
These are old. Newer versions are in the Boost CVS on the thread_dev
branch. I hope to move suitably modified versions of these and other
changes that William Kemp added to the thread_dev branch in the coming
weeks. In fact, see thread "Moving Boost.Thread barrier from thread_dev
to HEAD".
> Regards
> Serge
>
>
> _______________________________________________
> Unsubscribe & other changes: http://listarchives.boost.org/mailman/listinfo.cgi/boost
>