Re: Bug in emacs

[Kevin Rodgers]

era@iki.fi wrote:

> If you have macros which influence the meaning of forms you are
> compiling, the macro needs to be loaded before you compile. What you
> are reporting seems like a typical symptom of failing to load the
> macro in question before compiling.
>
> A workaround would be to make sure you eval the macro definition
> before compiling.
>
> I'm not sure what the bug really is. Perhaps it would be useful to get
> a warning when compiling / evaling something when a macro +is+ in
> effect and the file you are compiling is not pulling it in properly?
> Then at least you get a hint to fix it while you still can, while
> those who do it right will not experience any adverse effects.


When the compiler comes across a (function arg ...) form, either the
function is defined or it isn't.  If it's defined, either as a function
or a macro, all is well.  If it's not defined, the compiler can't know
whether it is a function or a macro and assumes it's a function.  A
macro can't be "in effect" if it's file was not loaded "properly".

The compiler does issue warnings when it encounters an undefined
macro/function:

While compiling the end of the data in file /home/kevinr/emacs/foo.el:
  ** the function bar is not known to be defined.

--
Kevin Rodgers