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

From: hinnant_at_[hidden]
Date: 2008-01-07 14:49:40

Author: hinnant
Date: 2008-01-07 14:49:39 EST (Mon, 07 Jan 2008)
New Revision: 42577
URL: http://svn.boost.org/trac/boost/changeset/42577

Log:
V1 issue 17.

Text files modified: 
   sandbox/committee/LWG/issues.html         |     2 +-                                      
   sandbox/committee/LWG/thread_library.html |     4 ++--                                    
   2 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-07 14:49:39 EST (Mon, 07 Jan 2008)
@@ -157,7 +157,7 @@
 "The
 expression ... shall be well-defined..." That last word should be
 &quot;well-formed&quot;. </p>
-<p>17. [thread.mutex.requirements] (30.3.1), effects of m.lock(): &quot;owns&quot;
+<p>&#9998; 17. [thread.mutex.requirements] (30.3.1), effects of m.lock(): &quot;owns&quot;
 isn't
 really clear. The front matter for mutexes talks about &quot;obtains
 ownership&quot; and

Modified: sandbox/committee/LWG/thread_library.html
==============================================================================
--- sandbox/committee/LWG/thread_library.html	(original)
+++ sandbox/committee/LWG/thread_library.html	2008-01-07 14:49:39 EST (Mon, 07 Jan 2008)
@@ -1279,8 +1279,8 @@
 <p>
 A mutex object facilitates protection against data races
 and allows thread-safe synchronization of data between threads.
-A thread obtains ownership of a mutex object by calling <code>lock()</code>
-and relinquishes ownership by calling <code>unlock()</code>.
+A thread owns a mutex from the time it successfully calls one of the
+lock functions until it calls <code>unlock</code>.
 Mutexes may be either recursive or non-recursive,
 and may grant simultaneous ownership to one or many threads.
 The mutex types supplied by the Standard Library