From: David Kastrup <dak@gnu.org>
To: guile-devel@gnu.org
Subject: Re: local-eval on syntax-local-binding, bound-identifiers
Date: Tue, 17 Jan 2012 11:55:45 +0100 [thread overview]
Message-ID: <87d3aitx72.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 8739bfi5ys.fsf@pobox.com
Andy Wingo <wingo@pobox.com> writes:
> What if instead we implemented closure serialization somehow? Then we
> would handle procedural macros too, and bound-identifiers would still be
> sufficient.
>
> Maybe that idea is a little too crazy.
Are we still talking about Scheme? The language with
call-with-current-continuation? "a little too crazy" is not a
criterion. "Too complex to work or or with" would be. Those are
related, but not necessarily the same.
--
David Kastrup
next prev parent reply other threads:[~2012-01-17 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 22:17 local-eval on syntax-local-binding, bound-identifiers Andy Wingo
2012-01-16 3:30 ` Mark H Weaver
2012-01-16 11:01 ` Andy Wingo
2012-01-16 13:28 ` Mark H Weaver
2012-01-16 15:17 ` Andy Wingo
2012-01-16 20:36 ` Mark H Weaver
2012-01-16 23:27 ` Andy Wingo
2012-01-17 10:55 ` David Kastrup [this message]
2012-01-19 11:55 ` 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=87d3aitx72.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=guile-devel@gnu.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).