|
Boost-Commit : |
From: bdawes_at_[hidden]
Date: 2007-12-14 16:52:04
Author: bemandawes
Date: 2007-12-14 16:52:03 EST (Fri, 14 Dec 2007)
New Revision: 42054
URL: http://svn.boost.org/trac/boost/changeset/42054
Log:
Per discussion on list, add description of condition_variable and condition_variable_any to introduction
Text files modified:
sandbox/committee/LWG/thread_library.html | 8 ++++++--
1 files changed, 6 insertions(+), 2 deletions(-)
Modified: sandbox/committee/LWG/thread_library.html
==============================================================================
--- sandbox/committee/LWG/thread_library.html (original)
+++ sandbox/committee/LWG/thread_library.html 2007-12-14 16:52:03 EST (Fri, 14 Dec 2007)
@@ -2823,9 +2823,13 @@
<h3><a name="thread.condition">30.4 Condition variables [thread.condition]</a></h3>
<p>
-Condition variables provide a synchronization primitive used to block a thread
+Condition variables provide synchronization primitives used to block a thread
until notified by some other thread that some condition is met or until a
-system time is reached.</p>
+system time is reached. Class <code>condition_variable</code> provides a
+condition variable that can only wait on a <code>unique_lock<mutex></code>,
+allowing maximum efficiency on some platforms. Class <code>
+condition_variable_any</code> provides a general condition variable that can
+wait on user supplied lock types.</p>
<p>
Condition variables permit concurrent invocation
Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk