From: Sebastian Tennant <sebyte@smolny.plus.com>
To: guile-user@gnu.org
Subject: Re: Dynamic variable binding
Date: Sat, 15 Nov 2008 16:59:45 +0000 [thread overview]
Message-ID: <hc68j56m.fsf@vps203.linuxvps.org> (raw)
In-Reply-To: 491EE39E.7090209@wilsonjc.us
Quoth Jon Wilson <jsw@wilsonjc.us>:
> Sebastian Tennant wrote:
>> Quoth ludo@gnu.org (Ludovic Courtès):
>>> Dynamic binding definition is compilation-unfriendly. Kjetil's
>>> proposed `define-lotsof' macro is more appropriate, as it can be fully
>>> evaluated at compile-time (should a compiler be used, that is),
>>> whereas the `module-define!' trick requires that compilation and
>>> execution be the one and same phase.
>>
>> Ah, interesting. Noted. Thanks again (to Kjetil also).
>
> Furthermore, the lack of separation between what is compiled and what
> is executed causes problems with defining a module system that
> understands hygiene. It took me a while to understand this, but
> finally sitting down and grokking Matthew Flatt's paper "Compilable
> and Composable Macros: You Want it When?" got it through my skull.
>
> http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.11.4008
This looks like a very useful (and comprehensive) paper. Thanks.
Sebastian
next prev parent reply other threads:[~2008-11-15 16:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 19:53 Dynamic variable binding Sebastian Tennant
2008-11-12 22:05 ` Ludovic Courtès
2008-11-13 0:51 ` Keith Wright
2008-12-19 11:50 ` Sebastian Tennant
2008-12-19 13:03 ` Ludovic Courtès
2008-12-19 15:46 ` Sebastian Tennant
2008-12-20 0:17 ` Keith Wright
2008-12-27 15:56 ` Sebastian Tennant
2008-12-28 22:56 ` Neil Jerram
2008-12-29 10:48 ` Sebastian Tennant
2008-11-13 11:33 ` Sebastian Tennant
2008-11-13 18:50 ` Ludovic Courtès
2008-11-14 6:14 ` Sebastian Tennant
2008-11-15 14:58 ` Jon Wilson
2008-11-15 16:59 ` Sebastian Tennant [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-12 22:37 dsmich
[not found] <200811130428.mAD4SQbi030880@cm-mail.stanford.edu>
2008-11-13 14:10 ` Kjetil S. Matheussen
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=hc68j56m.fsf@vps203.linuxvps.org \
--to=sebyte@smolny.plus.com \
--cc=guile-user@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).