doc: Link exceptions and escape continuations.

* doc/ref/api-control.texi (Prompt Primitives): Mention exceptions.
  (Exception Terminology): Link to `call/ec'.

1 files changed, 8 insertions, 1 deletions

diff --git a/doc/ref/api-control.texi b/doc/ref/api-control.texi
index 278a03dcb..56ffba26b 100644
--- a/doc/ref/api-control.texi
+++ b/doc/ref/api-control.texi
@@ -582,7 +582,9 @@ 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}.
+reason they are sometimes called @dfn{one-shot continuations}.  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.
@@ -1031,6 +1033,11 @@ to avoid the risk of confusion with POSIX signals.
 This manual prefers to speak of throwing and catching exceptions, since
 this terminology matches the corresponding Guile primitives.
 
+The exception mechanism described in this section has connections with
+@dfn{delimited continuations} (@pxref{Prompts}).  In particular,
+throwing an exception is akin to invoking an @dfn{escape continuation}
+(@pxref{Prompt Primitives, @code{call/ec}}).
+
 
 @node Catch
 @subsubsection Catching Exceptions