From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: eval-case and toplevel prohibitions
Date: Tue, 03 Mar 2009 07:31:11 +0000 [thread overview]
Message-ID: <87eixf3vwg.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <m3ocwjpmgw.fsf@pobox.com> (Andy Wingo's message of "Mon\, 02 Mar 2009 23\:51\:43 +0100")
Andy Wingo <wingo@pobox.com> writes:
> So I was thinking: why do we have this fetish for prohibiting certain
> forms in a non-toplevel context? I am of a mind to replace eval-case
> with eval-when, which is actually more expressive, as it allows us to
> discriminate the different phases in non-toplevel contexts as well.
I recall that Marius added the checks, but unfortunately not why.
Sorry! Does googling help?
Neil
next prev parent reply other threads:[~2009-03-03 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 22:51 eval-case and toplevel prohibitions Andy Wingo
2009-03-03 7:31 ` Neil Jerram [this message]
2009-03-04 8:48 ` Ludovic Courtès
2009-03-06 10:56 ` Andy Wingo
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=87eixf3vwg.fsf@arudy.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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).