summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndy Wingo <wingo@pobox.com>2016-06-24 18:18:46 +0200
committerAndy Wingo <wingo@pobox.com>2016-06-24 18:18:46 +0200
commit5f9134c32d0c4d7497dfeabbcc219e35a66013d5 (patch)
treea0e3f31442453154ac096acc7d534c67c610cfd1
parent6a5b44de683fdcea5aee7a089a294c597db55ca1 (diff)
downloadguile-5f9134c32d0c4d7497dfeabbcc219e35a66013d5.tar.gz
Favor "escape continuation" over "one-shot continuation" in manual
* doc/ref/api-control.texi (Prompt Primitives): Remove mention of one-shot continuations, as it's possible to invoke them multiple times if the continuation is re-entered through other means.
-rw-r--r--doc/ref/api-control.texi6
1 files changed, 2 insertions, 4 deletions
diff --git a/doc/ref/api-control.texi b/doc/ref/api-control.texi
index a1eacd6c8..10a445cb0 100644
--- a/doc/ref/api-control.texi
+++ b/doc/ref/api-control.texi
@@ -584,10 +584,8 @@ important efficiency consideration to keep in mind.
One example where this optimization matters is @dfn{escape
continuations}. Escape continuations are delimited continuations whose
only use is to make a non-local exit---i.e., to escape from the current
-continuation. Such continuations are invoked only once, and for this
-reason they are sometimes called @dfn{one-shot continuations}. A common
-use of escape continuations is when throwing an exception
-(@pxref{Exceptions}).
+continuation. A common use of escape continuations is when throwing an
+exception (@pxref{Exceptions}).
The constructs below are syntactic sugar atop prompts to simplify the
use of escape continuations.