Re: use of (defvar <foo>)

[Stefan Monnier <monnier@iro.umontreal.ca>]

>> From the future's point of view (Emacs-22 and up), placing such defvars
>> inside eval-when-compile is a bad practice (in the future it may even fail
>> to work since there's nothing that guarantees that the content of
>> eval-when-compile is actually compiled rather than just eval'd).

> Huh?  You don't want it compiled -- that's the point.

By "compiled" I only mean that it goes through the byte-compiler (before
being eval'd).  Not that the resulting byte-code is written in the
output file.

If the content of eval-when-compile were not compiled, then
(eval-when-compile (defvar foo)) would be 100% equivalent to a nop.
It's only because it's both compiled&eval'd that the byte-compiler notices
the defvar and thus silences warnings about subsequent uses of
this variable.

> You're actually considering changing what eval-when-compile does and
> breaking more existing code??

Compiling the content of eval-when-compile before eval'ing doesn't
remove/hide any bug AFAIK, quite the opposite.


        Stefan