From: Hans Aberg <haberg-1@telia.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: hygiene and macro-introduced toplevel bindings
Date: Mon, 4 Apr 2011 15:48:57 +0200 [thread overview]
Message-ID: <71A3FF72-9267-4DE6-8094-0959CC0BEA67@telia.com> (raw)
In-Reply-To: <m37hc8830g.fsf@unquote.localdomain>
On 9 Mar 2011, at 21:14, Andy Wingo wrote:
>> I want a syntax that allows one to explicitly choose which macro-bound
>> variables to export, but otherwise, they should never be visible outside
>> the macro (i.e., be uninterned). When exported, they will just have the
>> name indicated.
>
> You have that already in the form of datum->syntax. If you create a
> syntax object in the context of the incoming expression, it will be
> treated as if it originated with that expression.
Great!
Hans
next prev parent reply other threads:[~2011-04-04 13:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 21:37 hygiene and macro-introduced toplevel bindings Andy Wingo
2011-02-27 22:02 ` Hans Aberg
2011-02-28 0:15 ` Andreas Rottmann
2011-02-28 21:28 ` Andy Wingo
2011-02-28 21:49 ` Noah Lavine
2011-03-08 22:33 ` Andy Wingo
2011-02-28 22:32 ` Ludovic Courtès
2011-03-08 22:37 ` Andy Wingo
2011-03-09 9:33 ` Hans Aberg
2011-03-09 20:14 ` Andy Wingo
2011-04-04 13:48 ` Hans Aberg [this message]
2011-04-01 8:52 ` 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=71A3FF72-9267-4DE6-8094-0959CC0BEA67@telia.com \
--to=haberg-1@telia.com \
--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).