From: Kevin Ryde <user42@zip.com.au>
Subject: Re: continuation curiosity -- for entertainment purposes only
Date: Fri, 18 Jul 2003 08:56:48 +1000 [thread overview]
Message-ID: <87el0o3gpb.fsf@zip.com.au> (raw)
In-Reply-To: <200307161750.h6GHo7H00853@csserver.evansville.edu> (Stephen Compall's message of "Wed, 16 Jul 2003 12:50:07 -0500")
Stephen Compall <s11@member.fsf.org> writes:
>
> Imagine my surprise when it failed to consider the top-level
> expressions that report on next-match and run it if it's there as part
> of the flow, and skipped to what it hadn't executed --- the "quitting"
> message.
Is that because what's captured is a read-eval loop perhaps?
(Ie. expressions are read and evaluated one at a time, rather than an
eval of the whole file in one go.)
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2003-07-17 22:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 17:50 continuation curiosity -- for entertainment purposes only Stephen Compall
2003-07-17 22:56 ` Kevin Ryde [this message]
2003-07-24 20:58 ` goops: bug or not? Anders Vinjar
2003-07-25 9:03 ` Anders Vinjar
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=87el0o3gpb.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).