[clisp-list] Re: handler-bind macroexpansion and special operators (fwd)

[Hoehle, Joerg-C. <Joe...@t-...>]

Hi,

>>this macroexpansion will never be used by CLISP
>I can't understand how this could possibly work.

Maybe what's confusing us is that we have different uses of code-walkers in mind.

Maybe you think of something like XREF, which needs to find all functions, but does not care whether the macroexpanded code is slow or works at all.

I'm thinking of somethig like the current implementation of Iterate, where the result of full macroexpansion of the body will be integrated into the result of Iterate's own macroexpansion, so
a) it's essential that the expansion works and
b) it's sad when macroexpanded code leads to worse performance than direct compilation of the original form (but not too surprising).

Regards,
	Jorg Hohle.