[Boost-commit] svn:boost r42043 - sandbox/committee/LWG

From: hinnant_at_[hidden]
Date: 2007-12-14 13:59:59

Author: hinnant
Date: 2007-12-14 13:59:59 EST (Fri, 14 Dec 2007)
New Revision: 42043
URL: http://svn.boost.org/trac/boost/changeset/42043

Log:
V1 issues 29 and 30.

Text files modified: 
   sandbox/committee/LWG/issues.html         |     4 ++--                                    
   sandbox/committee/LWG/thread_library.html |     8 ++++++--                                
   2 files changed, 8 insertions(+), 4 deletions(-)

Modified: sandbox/committee/LWG/issues.html
==============================================================================
--- sandbox/committee/LWG/issues.html	(original)
+++ sandbox/committee/LWG/issues.html	2007-12-14 13:59:59 EST (Fri, 14 Dec 2007)
@@ -220,11 +220,11 @@
 see 24 (&quot;still&quot;), 25. </p>
 <p>&#9998; (19), &#9998; (20) 27. [thread.timedmutex.class] (30.3.2.1): see 19, 20. </p>
 <p>&#9998; (19), &#9998; (20) 28. [thread.timedmutex.recursive] (30.3.2.2): see 19, 20. </p>
-<p>29. [thread.lock.intro] (30.3.3), first paragraph: this would be
+<p>&#10004; 29. [thread.lock.intro] (30.3.3), first paragraph: this would be
 clearer in
 the singular: &quot;A lock is an object that holds a reference to a mutex and
 unlocks the mutex during the lock's destruction...&quot; </p>
-<p>30. [thread.lock.intro] (30.3.3), tag types: these are said to
+<p>&#9998; 30. [thread.lock.intro] (30.3.3), tag types: these are said to
 describe &quot;what
 should be done with the mutex&quot;, but their comments all talk about &quot;the
 lock&quot;.

Modified: sandbox/committee/LWG/thread_library.html
==============================================================================
--- sandbox/committee/LWG/thread_library.html	(original)
+++ sandbox/committee/LWG/thread_library.html	2007-12-14 13:59:59 EST (Fri, 14 Dec 2007)
@@ -1819,9 +1819,13 @@
 <h4><a name="thread.lock.intro">30.3.3 Locks [thread.lock.intro]</a></h4>
 
 <p>
-Locks are objects that hold a reference to a mutex
-and unlock the mutex during the lock's destruction
+A lock is an object that holds a reference to a mutex
+and may unlock the mutex during the lock's destruction
 (such as when leaving block scope).
+A thread of execution may use a lock to aid in managing
+mutex ownership in an exception safe manner.  A lock is
+said to <i>own a mutex</i> if it is currently managing 
+the mutex ownership for a thread of execution.
 The locks do not manage the lifetime of the mutex they
 reference, but only the ownership status of that mutex.
 [<i>Note:</i>