From: Stephen Compall <s11@member.fsf.org>
Cc: bug-guile@gnu.org
Subject: Re: [DOCPATCH]Revamp of doc/ref/scheme-control.texi
Date: 18 Jul 2003 12:14:13 -0500 [thread overview]
Message-ID: <xfywuef3ggq.fsf@csserver.evansville.edu> (raw)
In-Reply-To: <87isq03h0c.fsf@zip.com.au>
For your convenience, the URL is:
http://mail.gnu.org/archive/html/guile-devel/2003-07/msg00016.html
Kevin Ryde <user42@zip.com.au> writes:
> I posted a rewrite of this section to guile-devel last week, if you
> want to compare. (Subject "doco continuations".)
>
> I hadn't attempted to redo the example, mainly because I couldn't
> think of something that wasn't simply a loop or state machine in
> disguise.
1. IMHO, your explanation is better (albeit not as concise ;). Do you
want me to work this in and repost my patch, or would you rather do
it?
2. About the example: if you think it's too obvious, here's an idea: A
function performs a number of tests. When a test fails, it throws
an error, with REST (see the errors node) being the current
continuation. This gives the calling function an opportunity to
report the error, or hopefully fix it, and then resume executing
the testing function. You could emulate it with closures, sure,
but....
3. The above idea was one for another list: some "nifty" things you
can do with continuations. That is, as it is now, it vaguely
refers to situations in which call/cc may be preferable, without
explaining at least one of those situations.
--
Stephen Compall or s11 or sirian
You know the great thing about TV? If something important happens
anywhere at all in the world, no matter what time of the day or night,
you can always change the channel.
-- Jim Ignatowski
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2003-07-18 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 17:37 [DOCPATCH]Revamp of doc/ref/scheme-control.texi Stephen Compall
2003-07-17 22:50 ` Kevin Ryde
2003-07-18 17:14 ` Stephen Compall [this message]
2003-07-18 23:38 ` Kevin Ryde
2003-07-23 23:53 ` Kevin Ryde
2003-07-24 19:14 ` Stephen Compall
2003-07-25 22:37 ` Kevin Ryde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xfywuef3ggq.fsf@csserver.evansville.edu \
--to=s11@member.fsf.org \
--cc=bug-guile@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).