Fix bullet list.
diff --git a/asio/include/asio/basic_deadline_timer.hpp b/asio/include/asio/basic_deadline_timer.hpp index 62e49eb..eb0057e 100644 --- a/asio/include/asio/basic_deadline_timer.hpp +++ b/asio/include/asio/basic_deadline_timer.hpp
@@ -199,8 +199,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. */ @@ -226,8 +229,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. */ @@ -260,8 +266,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. */ @@ -288,8 +297,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. */ @@ -323,8 +335,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. */ @@ -351,8 +366,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. */
diff --git a/asio/src/doc/reference.qbk b/asio/src/doc/reference.qbk index cea61b5..a2e721d 100644 --- a/asio/src/doc/reference.qbk +++ b/asio/src/doc/reference.qbk
@@ -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 - -* 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. +If the timer has already expired when `cancel()` is called, then the handlers for asynchronous wait operations will: +* 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 - -* 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. +If the timer has already expired when `cancel()` is called, then the handlers for asynchronous wait operations will: +* 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 - -* 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. +If the timer has already expired when `expires_at()` is called, then the handlers for asynchronous wait operations will: +* 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 - -* 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. +If the timer has already expired when `expires_at()` is called, then the handlers for asynchronous wait operations will: +* 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 - -* 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. +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 +* 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 - -* 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. +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 +* 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]