|
Boost-Commit : |
From: hinnant_at_[hidden]
Date: 2008-01-06 19:03:46
Author: hinnant
Date: 2008-01-06 19:03:46 EST (Sun, 06 Jan 2008)
New Revision: 42561
URL: http://svn.boost.org/trac/boost/changeset/42561
Log:
Checked off V1 24, 25, 26.
Text files modified:
sandbox/committee/LWG/issues.html | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
Modified: sandbox/committee/LWG/issues.html
==============================================================================
--- sandbox/committee/LWG/issues.html (original)
+++ sandbox/committee/LWG/issues.html 2008-01-06 19:03:46 EST (Sun, 06 Jan 2008)
@@ -202,11 +202,11 @@
Instad of
"are required to", use "shall". </p>
<p>✔ (16) 23. [thread.timedmutex.requirements] (30.3.2): see 14, 16 </p>
-<p>✎ 24. [thread.timedmutex.requirements] (30.3.2), effects clause: "If the
+<p>✔ 24. [thread.timedmutex.requirements] (30.3.2), effects clause: "If the
indicated time duration is less than or equal to 0, the function still
attempts to obtain ownership without blocking" change "indicated" to
"requested" and remove "still". </p>
-<p>✎ 25. [thread.timedmutex.requirements] (30.3.2), effects clause: "If the
+<p>✔ 25. [thread.timedmutex.requirements] (30.3.2), effects clause: "If the
function returns within the specified time duration, it shall have
obtained
ownership." This sentence is awkward. I'd phrase it "The function
@@ -215,7 +215,7 @@
of the
mutex object." And even then, functions don't own mutex objects.
Threads do. </p>
-<p>✎ 26. [thread.timedmutex.requirements] (30.3.2), effects clause for
+<p>✔ 26. [thread.timedmutex.requirements] (30.3.2), effects clause for
timed_lock:
see 24 ("still"), 25. </p>
<p>✔ (19), ✔ (20) 27. [thread.timedmutex.class] (30.3.2.1): see 19, 20. </p>
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