[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #20941] Modules interact badly with macros
|
From: |
Ludovic Courtès |
|
Subject: |
[bug #20941] Modules interact badly with macros |
|
Date: |
Wed, 31 Oct 2007 09:15:27 +0000 |
|
User-agent: |
Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.8.1.6) Gecko/20070801 (Debian-1.8.1.6-1) Galeon/2.0.2 (Debian package 2.0.2-4) |
Follow-up Comment #2, bug #20941 (project guile):
The thing is, for engineering reasons, there are procedures used by macros
that you may not want to export. Or the macros you export may be using
procedures from other modules that you do not want to re-export. Overall, you
don't want to pollute the user's name space.
Worse, if the module user uses a renamer or a selector (e.g., "#:select
(the-macro-that-i-want)"), the macros just won't work.
Symbols used by macros should be resolved in the macro definition context,
not in its usage context (see "Composable and Compilable Macros: You Want it
When?" by M. Flatt).
FWIW, I used a hack to make "macros that work" in SRFI-35.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?20941>
_______________________________________________
Message posté via/par Savannah
http://savannah.gnu.org/