[Ecls-list] compiler-macro: spurious parameter reference?
Pascal J. Bourguignon
pjb at informatimago.com
Sun Aug 29 20:12:13 UTC 2010
Juan Jose Garcia-Ripoll <juanjose.garciaripoll at googlemail.com> writes:
> On Sun, Aug 29, 2010 at 6:37 PM, Pascal J. Bourguignon <pjb at informatimago.com> wrote:
>
> When compiling a compiler macro, the &whole form seems to be
> referenced even if it is not
>
> This actually happens with all macros. Macros destructure forms:
> they always get the whole form to be parsed in a &whole variable and
> only by inspecting this list can they gather the values of their
> arguments.
>
> The current code uses the name of the variable given by the user to
> store the form that is then parsed to assign values for each of the
> macro arguments.
>
> So, in the end, the &whole variable is always referenced, but this
> happens way before it reaches the code supplied by the user.
>
> I supposed I could complicate the macroexpansion adding yet another
> LET form with a &whole variable that is only seen by the user, but
> it does not seem so urgent.
It's not urgent at all, but keep in mind that ASDF is ticklish about
warnings...
--
__Pascal Bourguignon__ http://www.informatimago.com/
More information about the ecl-devel
mailing list