Re: Towards a cleaner build

[Lars Ingebrigtsen]

Stefan Monnier <address@hidden> writes:

>> But as a macro that expands to (basically) `progn', then the byte
>> compiler just sees the `progn' and is unable to do anything with the
>> form.
>
> You can use byte-compile-macro-environment to override the default
> definition of the macro during compilation.

I've been poking at the machinery here, and I'm not quite sure I
understand.  If I put a different definition of with-suppressed-warnings
into byte-compile-initial-macro-environment, then that will indeed
override the normal definition.

But that variable is consulted before compilation is done, and it can't
do any bindings that affect the compilation itself, I think?  I mean, it
can alter the global state, but not do any let bindings.

Or did you mean that that should return an intermediary function and
then do the byte-hunk-handler thing as in my code sketch?

*implements*

Oh, wow, that worked.  :-)  It always helps to ask, apparently.

But if you meant something else, please correct my new
misunderstanding.  I've created a new branch for this, and I'll push
when I've cleaned things up slightly.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no