[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Guile-commits] 02/02: Favor "escape continuation" over "one-shot contin
From: |
Andy Wingo |
Subject: |
[Guile-commits] 02/02: Favor "escape continuation" over "one-shot continuation" in manual |
Date: |
Fri, 24 Jun 2016 16:20:35 +0000 (UTC) |
wingo pushed a commit to branch master
in repository guile.
commit 5f9134c32d0c4d7497dfeabbcc219e35a66013d5
Author: Andy Wingo <address@hidden>
Date: Fri Jun 24 18:18:46 2016 +0200
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.
---
doc/ref/api-control.texi | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/doc/ref/api-control.texi b/doc/ref/api-control.texi
index a1eacd6..10a445c 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.