From: Kevin Ryde <user42@zip.com.au>
Subject: Re: while break and continue
Date: Tue, 29 Jul 2003 10:23:12 +1000 [thread overview]
Message-ID: <8765lmkwpb.fsf@zip.com.au> (raw)
In-Reply-To: <87smosrpp0.fsf@zagadka.ping.de> (Marius Vollmer's message of "27 Jul 2003 16:48:11 +0200")
Marius Vollmer <mvo@zagadka.de> writes:
>
> Do you want to put it into boot-9.scm?
Yes, I think it'd be good. Actually what I'd like to put in is
something like
(define-macro (while cond . body)
(let* ((key (make-symbol "while-key"))
(break-proc (lambda () (throw key #t)))
(continue-proc (lambda () (throw key #f))))
`(,do ((break ,break-proc)
(continue ,continue-proc))
((,catch (,quote ,key)
(,lambda ()
(,do ()
((,not ,cond))
,@body)
#t)
,(lambda (key arg) arg))))))
All the backquoting being designed to protect against local bindings
at expansion time. I know what you said about compiler friendliness,
but I think for the moment protection against local defines would be
better.
(I imagine a compiler might want to try to cooperate with application
macros like this using only basic list or procedure stuff, through
some sort of eval in a restricted environment or whatever. But no
doubt plenty of people smarter than me have thought about such things
before.)
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-07-29 0:23 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
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 [this message]
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=8765lmkwpb.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).