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

From: bdawes_at_[hidden]
Date: 2007-12-14 09:00:22

Author: bemandawes
Date: 2007-12-14 09:00:21 EST (Fri, 14 Dec 2007)
New Revision: 42030
URL: http://svn.boost.org/trac/boost/changeset/42030

Log:
V1 issue #18
Text files modified: 
   sandbox/committee/LWG/issues.html         |     2 +-                                      
   sandbox/committee/LWG/thread_library.html |    18 ++++++++----------                      
   2 files changed, 9 insertions(+), 11 deletions(-)

Modified: sandbox/committee/LWG/issues.html
==============================================================================
--- sandbox/committee/LWG/issues.html	(original)
+++ sandbox/committee/LWG/issues.html	2007-12-14 09:00:21 EST (Fri, 14 Dec 2007)
@@ -174,7 +174,7 @@
 defines the key term, without confusing the issue with the somewhat
 similar
 but irrelevant notion of &quot;ownership&quot;. </p>
-<p>18. [thread.mutex.requirements] (30.3.1), effects of m.try_lock(): the
+<p>&#10004; 18. [thread.mutex.requirements] (30.3.1), effects of m.try_lock(): the
 returns
 clause says that the implementation is allowed to fail even if the
 lock isn't

Modified: sandbox/committee/LWG/thread_library.html
==============================================================================
--- sandbox/committee/LWG/thread_library.html	(original)
+++ sandbox/committee/LWG/thread_library.html	2007-12-14 09:00:21 EST (Fri, 14 Dec 2007)
@@ -1382,7 +1382,13 @@
 Attempt to obtain ownership of the mutex for the current thread
 without blocking.
 If ownership is not obtained,
-there is no effect and <code>try_lock()</code> immediately returns.
+there is no effect and <code>try_lock()</code> immediately returns.&nbsp; An 
+implementation may fail to obtain the lock even if it is not held by any other 
+thread. [<i>Note:</i>
+This spurious failure is normally uncommon,
+but allows interesting implementations
+based on a simple <code>compare_swap</code> ([atomics.operations]).
+&mdash;<i>end note</i>]
 </dd>
 
 <dt>Return type:</dt>
@@ -1395,15 +1401,7 @@
 If ownership of the mutex was obtained for the current thread,
 <code>true</code>,
 otherwise,
-<code>false</code>.
-An implementation may fail to obtain the lock
-even if it is not held by any other thread.
-[<i>Note:</i>
-This spurious failure is normally uncommon,
-but allows interesting implementations
-based on a simple <code>compare_swap</code> ([atomics.operations]).
-&mdash;<i>end note</i>]
-</dd>
+<code>false</code>.</dd>
 
 <dt>Synchronization:</dt>
 <dd>