rif <[EMAIL PROTECTED]> writes: > I start CMUCL. I compile fftw-cmucl.lisp using C-c C-k in ILISP. I > get 33 notes. Everything seems fine. I don't load fftw-cmucl.x86. I > compile fftw-cmucl.lisp again. This time, 44 notes, and the notes > directly stem from the two type declarations I have in the file being > ignored. I can compile it as many times as I want, but after the > first compile, it seems that type declarations are ignored. If I kill > CMUCL and restart it, I can get 33 notes again on a first compile. > > If anyone has any ideas what causes this or how to fix it, I'd be very > grateful to hear them.
Compiling a file can have compile-time effects on the compiling Lisp. (Which, incidentally, is what makes incompatible changes in CMUCL itself difficult :).) Pick DEFMACRO as a simple example. Compiling a file containing a macro definition defines that macro in the compiling CMUCL. A second compilation will now start with that macro defined. I'd guess you are seeing something like that, not from a macro but from something else having a compile-time effect.
