diff options
author | Andrei Pavel <andrei.pavel@qualitance.com> | 2016-12-14 15:57:44 +0100 |
---|---|---|
committer | Andrei Pavel <andrei.pavel@qualitance.com> | 2016-12-14 15:57:44 +0100 |
commit | 9082500187f9e0ebf99d5ecb67d7e815a7da2239 (patch) | |
tree | 39147bea0dd7b1bec3b93c47b927cb55eac4a767 /ext | |
parent | [master] Addressed doxygen warnings raised. (diff) | |
download | kea-9082500187f9e0ebf99d5ecb67d7e815a7da2239.tar.xz kea-9082500187f9e0ebf99d5ecb67d7e815a7da2239.zip |
Corrected typos
Diffstat (limited to 'ext')
-rw-r--r-- | ext/coroutine/coroutine.h | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/ext/coroutine/coroutine.h b/ext/coroutine/coroutine.h index 985888bf13..0f36c3f890 100644 --- a/ext/coroutine/coroutine.h +++ b/ext/coroutine/coroutine.h @@ -15,22 +15,22 @@ // \brief Coroutine object // // A coroutine object maintains the state of a re-enterable routine. It -// is assignable and copy-constructable, and can be used as a base class +// is assignable and copy-constructible, and can be used as a base class // for a class that uses it, or as a data member. The copy overhead is // a single int. // -// A reenterable function contains a CORO_REENTER (coroutine) { ... } +// A reentrant function contains a CORO_REENTER (coroutine) { ... } // block. Whenever an asychrnonous operation is initiated within the // routine, the function is provided as the handler object. (The simplest -// way to do this is to have the reenterable function be the operator() +// way to do this is to have the reentrant function be the operator() // member for the coroutine object itself.) For example: -// +// // CORO_YIELD socket->async_read_some(buffer, *this); // // The CORO_YIELD keyword updates the current status of the coroutine to // indicate the line number currently being executed. The // async_read_some() call is initiated, with a copy of the updated -// corotutine as its handler object, and the current coroutine exits. When +// coroutine as its handler object, and the current coroutine exits. When // the async_read_some() call finishes, the copied coroutine will be // called, and will resume processing exactly where the original one left // off--right after asynchronous call. This allows asynchronous I/O |