From: Andy Wingo <wingo@pobox.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: syntax-local-binding
Date: Fri, 20 Jan 2012 22:23:04 +0100 [thread overview]
Message-ID: <87r4yurruv.fsf@pobox.com> (raw)
In-Reply-To: <87sjjaunme.fsf@netris.org> (Mark H. Weaver's message of "Fri, 20 Jan 2012 15:26:17 -0500")
On Fri 20 Jan 2012 21:26, Mark H Weaver <mhw@netris.org> writes:
> Andy Wingo <wingo@pobox.com> writes:
>> `lexical'
>> A lexically-bound variable. The value is a unique token (in
>> the sense of `eq?') identifying this binding.
>>
>> `macro'
>> A syntax transformer, either local or global. The value is
>> the transformer procedure.
>
> Ironically, `syntax-local-binding' renders the current simple
> implementation strategy of `the-environment' inadequate, because
> identifier-syntax is no longer sufficient to simulate a lexical.
Why do you say that?
> In particular, I was hoping to change the binding representation of
> `syntax-rules' macros so that they are serializable. In particular,
> they would be represented by the `syntax-rules' form itself (the same
> one that psyntax currently passes to `primitive-eval' to produce the
> transformer procedure). A weak-key hash table would cache the compiled
> transformer procedures.
>
> This would allow (the-environment) to capture locally-bound
> `syntax-rules' macros. Unfortunately, `syntax-local-binding', as
> currently documented, now makes this impossible.
Why do you think that? The procedures do carry metadata; I understood
that that was your strategy, to use the serialization of the
syntax-rules form in the procedure metadata.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2012-01-20 21:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 17:00 syntax-local-binding Andy Wingo
2012-01-15 17:22 ` syntax-local-binding Andy Wingo
2012-01-19 11:41 ` syntax-local-binding Andy Wingo
2012-01-20 20:26 ` syntax-local-binding Mark H Weaver
2012-01-20 21:23 ` Andy Wingo [this message]
2012-01-20 22:03 ` syntax-local-binding Mark H Weaver
2012-01-22 0:03 ` syntax-local-binding Ludovic Courtès
2012-01-23 16:05 ` syntax-local-binding Andy Wingo
2012-01-23 21:03 ` syntax-local-binding Mark H Weaver
2012-01-23 22:19 ` syntax-local-binding Andy Wingo
2012-01-24 2:11 ` syntax-local-binding Mark H Weaver
2012-01-24 11:42 ` syntax-local-binding Andy Wingo
2012-01-24 17:29 ` syntax-local-binding Noah Lavine
2012-01-24 10:30 ` syntax-local-binding Peter TB Brett
2012-01-24 10:38 ` syntax-local-binding David Kastrup
2012-01-24 11:26 ` syntax-local-binding Andy Wingo
2012-01-24 13:25 ` syntax-local-binding Mark H Weaver
2012-01-24 20:28 ` mark uniqueness (Was: Re: syntax-local-binding) Andy Wingo
2012-01-25 0:26 ` mark uniqueness Mark H Weaver
2012-01-25 9:02 ` Andy Wingo
2012-01-24 21:22 ` syntax-local-binding Andy Wingo
2012-01-25 2:30 ` syntax-local-binding Mark H Weaver
2012-01-25 7:49 ` syntax-local-binding Stefan Israelsson Tampe
2012-01-25 11:18 ` syntax-local-binding Andy Wingo
2012-01-25 13:18 ` syntax-local-binding Ludovic Courtès
2012-01-25 18:08 ` syntax-local-binding Mark H Weaver
2012-01-26 11:21 ` syntax-local-binding 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=87r4yurruv.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
/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).