From 5a0c9f69c8313d9a32e6785f573c2fbe25574d95 Mon Sep 17 00:00:00 2001 From: Mikael Djurfeldt Date: Sun, 13 Aug 2000 03:44:52 +0000 Subject: [PATCH] *** empty log message *** --- devel/translation/langtools.text | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/devel/translation/langtools.text b/devel/translation/langtools.text index 1c776e383..858b32b67 100644 --- a/devel/translation/langtools.text +++ b/devel/translation/langtools.text @@ -1,6 +1,6 @@ * Introduction -Version: $Id: langtools.text,v 1.2 2000-08-13 02:31:46 mdj Exp $ +Version: $Id: langtools.text,v 1.3 2000-08-13 03:44:52 mdj Exp $ This is a proposal for how Guile could interface with language translators. It will be posted on the Guile list and revised for some @@ -398,10 +398,9 @@ Return a THUNK which can be called repeatedly like this: THUNK --> SCHEMECODE -Each call will yield a new piece of scheme code. #f is returned -to signal the end of the stream of scheme expressions. (Note that -it isn't meaningful for THUNK to return immediates. In fact, it's -only meaningful to return expressions with side-effects.) +Each call will yield a new piece of scheme code. The THUNK signals +end of translation by returning the unique value *end-of-translation* +which can be tested using the predicate `end-of-translation?'. The optional argument ALIST provides compilation options for the translator: