From: Marius Vollmer <mvo@zagadka.de>
Subject: Re: while break and continue
Date: 02 Jun 2003 01:58:35 +0200 [thread overview]
Message-ID: <87he79ic44.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87isrtmhfw.fsf@zip.com.au>
Kevin Ryde <user42@zip.com.au> writes:
> I was going to add some words to the manual about break and continue
> in a while loop, but noticed continue doesn't do what I might have
> thought.
Oops. Yes, that is unexpected. I think your solution is essentially
correct, except that you shouldn't use procedure->memoizing-macro (use
define-macro instead) and that you inject literal procedures into the
expanded code. This is not good style since the procedures are
created in the compile time environment but used in the run-time
environment. A compiler might not like this.
This old post might be interesting as well, but the 'tagbody'
implementation in it is not properly tail recursive:
http://sources.redhat.com/ml/guile/2000-07/msg00339.html
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-06-01 23:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-30 0:00 while break and continue Kevin Ryde
2003-06-01 23:58 ` Marius Vollmer [this message]
2003-06-05 1:42 ` Kevin Ryde
2003-06-18 22:56 ` Marius Vollmer
2003-06-21 23:28 ` Kevin Ryde
2003-07-27 14:48 ` Marius Vollmer
2003-07-29 0:23 ` Kevin Ryde
2003-08-13 21:49 ` Kevin Ryde
2003-08-13 9:27 ` Matthias Koeppe
2003-08-14 23:35 ` Kevin Ryde
2003-08-15 1:43 ` Kevin Ryde
2003-06-06 22:31 ` Kevin Ryde
2003-06-18 22:57 ` Marius Vollmer
2003-06-20 23:56 ` 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=87he79ic44.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
/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).