guile-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Guile-commits] 10/11: Favor "escape continuation" over "one-shot contin


From: Andy Wingo
Subject: [Guile-commits] 10/11: Favor "escape continuation" over "one-shot continuation" in manual
Date: Sun, 26 Jun 2016 20:58:18 +0000 (UTC)

wingo pushed a commit to branch stable-2.0
in repository guile.

commit da0f1eadaa19768c677fe4cde7dc4af726f78c9c
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 70a915b..7cc6cf7 100644
--- a/doc/ref/api-control.texi
+++ b/doc/ref/api-control.texi
@@ -581,10 +581,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.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]