summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorroot <root>2008-11-14 05:27:08 +0000
committerroot <root>2008-11-14 05:27:08 +0000
commitd5cb59151afca5d4202e69a4d27df78b35f259b4 (patch)
treee52c1dcec49b65422bc97230483e7407707e8c83
parented699927c14e407cf3c2693c91bcf7d3219c3c32 (diff)
*** empty log message ***
-rw-r--r--coro.h6
1 files changed, 4 insertions, 2 deletions
diff --git a/coro.h b/coro.h
index b03c159..d16f82b 100644
--- a/coro.h
+++ b/coro.h
@@ -149,7 +149,7 @@ typedef struct coro_context coro_context;
* Allocating/deallocating the stack is your own responsibility.
*
* As a special case, if coro, arg, sptr and ssize are all zero,
- * then an "empty" coro_contetx will be created that is suitable
+ * then an "empty" coro_context will be created that is suitable
* as an initial source for coro_transfer.
*
* This function is not reentrant, but putting a mutex around it
@@ -174,7 +174,9 @@ void coro_transfer (coro_context *prev, coro_context *next);
/*
* The following prototype defines the coroutine destroy function. It is
* usually implemented as a macro, so watch out. It also serves
- * no purpose unless you want to use the CORO_PTHREAD backend.
+ * no purpose unless you want to use the CORO_PTHREAD backend,
+ * where it is used to clean up the thread. You are responsible
+ * for freeing the stack and the context itself.
*
* This function is thread-safe and reentrant.
*/