[Boost-commit] svn:boost r55060 - in branches/release: . boost/asio libs/asio/doc

Subject: [Boost-commit] svn:boost r55060 - in branches/release: . boost/asio libs/asio/doc
From: chris_at_[hidden]
Date: 2009-07-21 08:45:12

Author: chris_kohlhoff
Date: 2009-07-21 08:45:11 EDT (Tue, 21 Jul 2009)
New Revision: 55060
URL: http://svn.boost.org/trac/boost/changeset/55060

Log:
Fix bullet list.

Properties modified: 
   branches/release/   (props changed)
Text files modified: 
   branches/release/boost/asio/basic_deadline_timer.hpp |    18 +++++++++++++++++                       
   branches/release/libs/asio/doc/reference.qbk         |    42 ++++++++++++++++++++++----------------- 
   2 files changed, 42 insertions(+), 18 deletions(-)

Modified: branches/release/boost/asio/basic_deadline_timer.hpp
==============================================================================
--- branches/release/boost/asio/basic_deadline_timer.hpp	(original)
+++ branches/release/boost/asio/basic_deadline_timer.hpp	2009-07-21 08:45:11 EDT (Tue, 21 Jul 2009)
@@ -200,8 +200,11 @@
    *
    * @note If the timer has already expired when cancel() is called, then the
    * handlers for asynchronous wait operations will:
+   *
    * @li have already been invoked; or
+   *
    * @li have been queued for invocation in the near future.
+   *
    * These handlers can no longer be cancelled, and therefore are passed an
    * error code that indicates the successful completion of the wait operation.
    */
@@ -227,8 +230,11 @@
    *
    * @note If the timer has already expired when cancel() is called, then the
    * handlers for asynchronous wait operations will:
+   *
    * @li have already been invoked; or
+   *
    * @li have been queued for invocation in the near future.
+   *
    * These handlers can no longer be cancelled, and therefore are passed an
    * error code that indicates the successful completion of the wait operation.
    */
@@ -261,8 +267,11 @@
    *
    * @note If the timer has already expired when expires_at() is called, then
    * the handlers for asynchronous wait operations will:
+   *
    * @li have already been invoked; or
+   *
    * @li have been queued for invocation in the near future.
+   *
    * These handlers can no longer be cancelled, and therefore are passed an
    * error code that indicates the successful completion of the wait operation.
    */
@@ -289,8 +298,11 @@
    *
    * @note If the timer has already expired when expires_at() is called, then
    * the handlers for asynchronous wait operations will:
+   *
    * @li have already been invoked; or
+   *
    * @li have been queued for invocation in the near future.
+   *
    * These handlers can no longer be cancelled, and therefore are passed an
    * error code that indicates the successful completion of the wait operation.
    */
@@ -324,8 +336,11 @@
    *
    * @note If the timer has already expired when expires_from_now() is called,
    * then the handlers for asynchronous wait operations will:
+   *
    * @li have already been invoked; or
+   *
    * @li have been queued for invocation in the near future.
+   *
    * These handlers can no longer be cancelled, and therefore are passed an
    * error code that indicates the successful completion of the wait operation.
    */
@@ -352,8 +367,11 @@
    *
    * @note If the timer has already expired when expires_from_now() is called,
    * then the handlers for asynchronous wait operations will:
+   *
    * @li have already been invoked; or
+   *
    * @li have been queued for invocation in the near future.
+   *
    * These handlers can no longer be cancelled, and therefore are passed an
    * error code that indicates the successful completion of the wait operation.
    */

Modified: branches/release/libs/asio/doc/reference.qbk
==============================================================================
--- branches/release/libs/asio/doc/reference.qbk	(original)
+++ branches/release/libs/asio/doc/reference.qbk	2009-07-21 08:45:11 EDT (Tue, 21 Jul 2009)
@@ -7597,14 +7597,15 @@
 
 [heading Remarks]
       
-If the timer has already expired when `cancel()` is called, then the handlers for asynchronous wait operations will: 
-* have already been invoked; or 
+If the timer has already expired when `cancel()` is called, then the handlers for asynchronous wait operations will:
 
-* have been queued for invocation in the near future. These handlers can no longer be cancelled, and therefore are passed an error code that indicates the successful completion of the wait operation. 
 
+* have already been invoked; or
 
 
+* have been queued for invocation in the near future.
 
+These handlers can no longer be cancelled, and therefore are passed an error code that indicates the successful completion of the wait operation. 
 
 
 [endsect]
@@ -7643,14 +7644,15 @@
 
 [heading Remarks]
       
-If the timer has already expired when `cancel()` is called, then the handlers for asynchronous wait operations will: 
-* have already been invoked; or 
+If the timer has already expired when `cancel()` is called, then the handlers for asynchronous wait operations will:
 
-* have been queued for invocation in the near future. These handlers can no longer be cancelled, and therefore are passed an error code that indicates the successful completion of the wait operation. 
 
+* have already been invoked; or
 
 
+* have been queued for invocation in the near future.
 
+These handlers can no longer be cancelled, and therefore are passed an error code that indicates the successful completion of the wait operation. 
 
 
 [endsect]
@@ -7758,14 +7760,15 @@
 
 [heading Remarks]
       
-If the timer has already expired when `expires_at()` is called, then the handlers for asynchronous wait operations will: 
-* have already been invoked; or 
+If the timer has already expired when `expires_at()` is called, then the handlers for asynchronous wait operations will:
 
-* have been queued for invocation in the near future. These handlers can no longer be cancelled, and therefore are passed an error code that indicates the successful completion of the wait operation. 
 
+* have already been invoked; or
 
 
+* have been queued for invocation in the near future.
 
+These handlers can no longer be cancelled, and therefore are passed an error code that indicates the successful completion of the wait operation. 
 
 
 [endsect]
@@ -7805,14 +7808,15 @@
 
 [heading Remarks]
       
-If the timer has already expired when `expires_at()` is called, then the handlers for asynchronous wait operations will: 
-* have already been invoked; or 
+If the timer has already expired when `expires_at()` is called, then the handlers for asynchronous wait operations will:
 
-* have been queued for invocation in the near future. These handlers can no longer be cancelled, and therefore are passed an error code that indicates the successful completion of the wait operation. 
 
+* have already been invoked; or
 
 
+* have been queued for invocation in the near future.
 
+These handlers can no longer be cancelled, and therefore are passed an error code that indicates the successful completion of the wait operation. 
 
 
 [endsect]
@@ -7899,14 +7903,15 @@
 
 [heading Remarks]
       
-If the timer has already expired when `expires_from_now()` is called, then the handlers for asynchronous wait operations will: 
-* have already been invoked; or 
+If the timer has already expired when `expires_from_now()` is called, then the handlers for asynchronous wait operations will:
 
-* have been queued for invocation in the near future. These handlers can no longer be cancelled, and therefore are passed an error code that indicates the successful completion of the wait operation. 
 
+* have already been invoked; or
 
 
+* have been queued for invocation in the near future.
 
+These handlers can no longer be cancelled, and therefore are passed an error code that indicates the successful completion of the wait operation. 
 
 
 [endsect]
@@ -7946,14 +7951,15 @@
 
 [heading Remarks]
       
-If the timer has already expired when `expires_from_now()` is called, then the handlers for asynchronous wait operations will: 
-* have already been invoked; or 
+If the timer has already expired when `expires_from_now()` is called, then the handlers for asynchronous wait operations will:
 
-* have been queued for invocation in the near future. These handlers can no longer be cancelled, and therefore are passed an error code that indicates the successful completion of the wait operation. 
 
+* have already been invoked; or
 
 
+* have been queued for invocation in the near future.
 
+These handlers can no longer be cancelled, and therefore are passed an error code that indicates the successful completion of the wait operation. 
 
 
 [endsect]