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

From: Lawrence_at_[hidden]
Date: 2007-12-09 15:31:37

Author: crowl
Date: 2007-12-09 15:31:36 EST (Sun, 09 Dec 2007)
New Revision: 41935
URL: http://svn.boost.org/trac/boost/changeset/41935

Log:
Add line breaks.

Text files modified: 
   sandbox/committee/LWG/thread_library.html |    36 ++++++++++++++++++++++++------------    
   1 files changed, 24 insertions(+), 12 deletions(-)

Modified: sandbox/committee/LWG/thread_library.html
==============================================================================
--- sandbox/committee/LWG/thread_library.html	(original)
+++ sandbox/committee/LWG/thread_library.html	2007-12-09 15:31:36 EST (Sun, 09 Dec 2007)
@@ -1275,7 +1275,8 @@
 either recursive or non-recursive, and may grant simultaneous ownership to one 
 or many threads. The mutex types supplied by the Standard Library 
 provide exclusive ownership semantics: only one thread may own the mutex at a 
-time. Both recursive and non-recursive mutexes are supplied.</p>
+time. Both recursive and non-recursive mutexes are supplied.
+</p>
 
 <p>
 This section describes requirements on template argument types
@@ -1316,10 +1317,13 @@
 <dt>Effects:</dt>
 <dd>
 The current thread will block until ownership of the mutex can be obtained for 
-the current thread.</dd>
+the current thread.
+</dd>
 
 <dt>Postconditions:</dt>
-<dd>The current thread owns the mutex.</dd>
+<dd>
+The current thread owns the mutex.
+</dd>
 
 <dt>Return type:</dt>
 <dd>
@@ -1412,7 +1416,8 @@
 
 <dt>Effects:</dt>
 <dd>
-Releases the current thread's ownership of the mutex.</dd>
+Releases the current thread's ownership of the mutex.
+</dd>
 
 <dt>Return type:</dt>
 <dd>
@@ -1462,16 +1467,19 @@
 <p>
 The class <code>mutex</code> provides a non-recursive mutex with exclusive 
 ownership semantics. It satisfies all the Mutex requirements ([thread.mutex.requirements]). 
-It shall be a standard-layout class ([class]).</p>
+It shall be a standard-layout class ([class]).
+</p>
 
 <p>
 If one thread owns the <code>mutex</code> object, attempts by another thread to 
 acquire ownership will fail (for <code>try_lock()</code>) or block (<code>for 
 lock()</code>) until the first thread has released ownership with a call to
-<code>unlock()</code>.</p>
+<code>unlock()</code>.
+</p>
 
 <p>
-It is undefined behavior:</p>
+It is undefined behavior:
+</p>
 
 <ul>
   <li>for a thread to call <code>lock()</code> or <code>try_lock()</code> if it 
@@ -1510,13 +1518,15 @@
 <p>
 The class <code>recursive_mutex</code> provides a recursive mutex with exclusive 
 ownership semantics. It satisfies all the Mutex requirements ([thread.mutex.requirements]). 
-It shall be a standard-layout class ([class]).</p>
+It shall be a standard-layout class ([class]).
+</p>
 
 <p>
 If one thread owns the <code>recursive_mutex</code> object, attempts by another 
 thread to acquire ownership will fail (for <code>try_lock()</code>) or block 
 (for <code>lock()</code>) until the first thread has completely released 
-ownership.</p>
+ownership.
+</p>
 
 <p>
 A thread that owns a <code>recursive_mutex</code> object may acquire additional 
@@ -1528,10 +1538,12 @@
 of type <code>system_error</code>. A thread must call <code>unlock()</code> once 
 for each level of ownership acquired by calls to <code>lock()</code> and <code>
 try_lock()</code>. Only when all levels of ownership have been released may 
-ownership be acquired by another thread.</p>
+ownership be acquired by another thread.
+</p>
 
 <p>
-It is undefined behavior</p>
+It is undefined behavior
+</p>
 
 <ul>
   <li>if a thread terminates while owning a <code>recursive_mutex</code> object.</li>
@@ -4985,4 +4997,4 @@
 </p>
 
 </body>
-</html>
\ No newline at end of file
+</html>