From: Kevin Ryde <user42@zip.com.au>
Subject: Re: while break and continue
Date: Sat, 07 Jun 2003 08:31:40 +1000 [thread overview]
Message-ID: <87isri25yr.fsf@zip.com.au> (raw)
In-Reply-To: 87he79ic44.fsf@zagadka.ping.de
Marius Vollmer <mvo@zagadka.de> writes:
>
> inject literal procedures into the expanded code.
Yes, that was for some wrong reasons.
On this subject though, is it worth expanding to actual procedures
rather than symbols, so one gets the intended effect irrespective of
local bindings at the point used?
I don't suppose anyone goes out of their way to shadow standard stuff,
but it's probably nice to take precautions.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-06-06 22:31 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
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 [this message]
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=87isri25yr.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).