Re: Byte compiler and eval-when-compile

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

> Could you maybe take a look at the end of eieio.el? I don't understand
> why the compiler warns that `eieio-update-lisp-imenu-expression' is
> undefined (he actually always did that, not only since your last
> change).

Because there's a call to eieio-update-lisp-imenu-expression even tho
the function is not always defined (it's only defined within an `if').

Admittedly, it's obvious to the reader that the call can only happen
when the function is defined, but the byte-compiler is pretty dumb in
this respect and doesn't see the connection.

> I'm also not sure what's the fix here - why did you wrap the
> check for (boundp 'lisp-imenu-generic-expression) in an
> `eval-when-compile'?

I didn't wrap it in eval-when-compile.  The only change I installed was
to fix a typo ("list"->"lisp").


        Stefan