From: Kevin Ryde <user42@zip.com.au>
Cc: bug-guile@gnu.org
Subject: Re: [DOCPATCH]Revamp of doc/ref/scheme-control.texi
Date: Fri, 18 Jul 2003 08:50:11 +1000 [thread overview]
Message-ID: <87isq03h0c.fsf@zip.com.au> (raw)
In-Reply-To: <200307161737.h6GHbb200806@csserver.evansville.edu> (Stephen Compall's message of "Wed, 16 Jul 2003 12:37:37 -0500")
Stephen Compall <s11@member.fsf.org> writes:
>
> (Continuations): Tried to explain them, and created full, useful,
> working example.
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.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2003-07-17 22:50 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 [this message]
2003-07-18 17:14 ` Stephen Compall
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=87isq03h0c.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).