Re: Another bug with the macro counter

[David Kastrup]

Stefan <address@hidden> writes:

>> + ;; Quiet the compiler.
>> + (defvar edebug-active) 
>> + 
>
> I'm not sure this is right.  I think such defvars should only be put when we
> know from circumstancial evidence (that the byte-compiler does not have
> access to) that the variable will be available.  If we need to check with
> `boundp', I find it's better not to put a `defvar' (and to rely on the (if
> (boundp 'foo) foo) form recognized by the byte-compiler).

Quieting the byte compiler can probably also be achieved with
(eval-when-compile (defvar edebug-active))

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum