From: Iain.Hanson_at_[hidden]
Date: 2001-07-31 10:14:54
I did not mean to imply that the null_mutex was required prior to
threads being submitted. At the moment I'm just trying to flesh out
the requirements and start on layer 1 design.
If I do need a null_mutex, I can easily roll my own and will happily
submitt it for addition to threads as and when you want it.
/ikh
______________________________ Reply Separator _________________________________
Subject: Re: [boost] Re: sockets /network programming Requirements
Author: williamkempf (williamkempf_at_[hidden]) at unix,mime
Date: 31/07/01 15:50
> In addition to exception saftey, this library needs to be
thread safe
> by design. This means that in order to follow the C++
principle of
> 'you only pay for what you use', we will need a null_mutex fro
boost
> threads.
If you don't use boost::condition with the mutex a null_mutex type can
be coded up with out any effort at all (and in fact such a mutex can
not be safely used with a condition variable). For that reason I've
not included this type in Boost.Threads. It's important that we get
Boost.Threads accepted quickly, and this means I need to keep the
library "minimal but complete" for the initial submission. There are
numerous other types that I expect to add to Boost.Threads later, and
this includes a null_mutex. In the mean time I'd suggest either
coding your own or using conditional compilation instead of the
Strategized Locking pattern.
Bill Kempf
Info: http://www.boost.org Unsubscribe: <mailto:boost-unsubscribe_at_yahoogroups.c
om>
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Visit our website at http://www.ubswarburg.com
This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.