summaryrefslogtreecommitdiff
path: root/doc/ref/scheme-control.texi
diff options
context:
space:
mode:
authorKevin Ryde <user42@zip.com.au>2004-04-05 23:14:55 +0000
committerKevin Ryde <user42@zip.com.au>2004-04-05 23:14:55 +0000
commitf1c6bec63708bfc14ee799d5cd4f9f1cbe5aa67b (patch)
tree3324dbcfa9c28fb2c04f0622c6bba46c497883a9 /doc/ref/scheme-control.texi
parentad22fe7cf87998a79234f9ca96f8c871333ef98e (diff)
downloadguile-f1c6bec63708bfc14ee799d5cd4f9f1cbe5aa67b.tar.gz
Tweak a few words from:
(Continuations): Rewrite with more detail.
Diffstat (limited to 'doc/ref/scheme-control.texi')
-rw-r--r--doc/ref/scheme-control.texi10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/ref/scheme-control.texi b/doc/ref/scheme-control.texi
index 7d7662c53..4a09f1d1d 100644
--- a/doc/ref/scheme-control.texi
+++ b/doc/ref/scheme-control.texi
@@ -474,7 +474,7 @@ represented by the continuation.
A continuation is like a dynamic label, capturing at run-time a point
in program execution, including all the nested calls that have lead to
-it, or rather the code that will execute when those calls return.
+it (or rather the code that will execute when those calls return).
Continuations are created with the following functions.
@@ -561,10 +561,10 @@ a function returning more times than it was called. It may help
instead to think of it being stealthily re-entered and then program
flow going on as normal.
-The functions @code{dynamic-wind} (@pxref{Dynamic Wind}) can be used to
-ensure setup and cleanup code is run when a program locus is resumed or
-abandoned through the continuation mechanism. C code can use
-@dfn{frames} (@pxref{Frames}).
+@code{dynamic-wind} (@pxref{Dynamic Wind}) can be used to ensure setup
+and cleanup code is run when a program locus is resumed or abandoned
+through the continuation mechanism. C code can use @dfn{frames}
+(@pxref{Frames}).
@sp 1
Continuations are a powerful mechanism, and can be used to implement