On Sat, Nov 20, 2010 at 11:04 AM, Erik Huelsmann ehuels@gmail.com wrote:
Hi Alessio,
I think the key is a bit higher up; something must be causing quicklisp to load precompiler.lisp, but not the actual compiler.
Higher up, there's an expression (fset ...); I'm not sure, but I think that might be returning the expression, not the function name.
Yes, I see. Actually if I understand it correctly it will only be used in file compilation; yet it could cause problems with "strange" forms like (setq foo (defun ...)) where foo will be set to the function object instead of the function name, only when loading the FASL, not when loading the source. I'll experiment a bit with this and if I'm right, I'll commit another fix.
Thanks for the tip!
Later, Alessio