|
Boost-Commit : |
From: hinnant_at_[hidden]
Date: 2007-12-09 11:39:45
Author: hinnant
Date: 2007-12-09 11:39:44 EST (Sun, 09 Dec 2007)
New Revision: 41924
URL: http://svn.boost.org/trac/boost/changeset/41924
Log:
Checked off Pete issue 32.
Text files modified:
sandbox/committee/LWG/Pete_comments.html | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
Modified: sandbox/committee/LWG/Pete_comments.html
==============================================================================
--- sandbox/committee/LWG/Pete_comments.html (original)
+++ sandbox/committee/LWG/Pete_comments.html 2007-12-09 11:39:44 EST (Sun, 09 Dec 2007)
@@ -199,7 +199,7 @@
requirements. i.e. "Mutex concepts" -> "Mutex requirements". (Added by
Beman.)<br>
</li>
- <li>Anthony's wording [for issue 24] nails the problem
+ <li>✔ Anthony's wording [for issue 24] nails the problem
for condition_variable, but we have the same problem with
condition_variable_any, and this looks more problematic. I was hoping that
condition_variable_any::wait would require only lock() and unlock() on the
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