MS> Ah, now I see what you meant. Unfortunately, this approach works MS> only with self-quoting values for BAR: What Common Lisp are you using ? USER(8): (setq bar #'(lambda (x) x)) #<Interpreted Function (unnamed) ＠ #x8cf772> USER(9): (defmacro foo () bar) FOO USER(10): (let ((bar #'(lambda (x) (+ x 1)))) (funcall (foo) 23)) 23 This is Allegro Common Lisp 4.3. I think that it should be pretty close to ANSI Cl requirements. I bet CMUCL is somewhat more explanative than ACL (note however that CMUCL as of 17f does not implement ANSI CL, although 18 is said to move towards ANSI compliance). MS> Consequently, what you're doing is really an accidental hack. If you are using CLisp, I think we have just found a reason why it might not be the best candidate for a new CL-based Lisp Engine after all. Holger -- --- http://www.coling.uni-freiburg.de/~schauer --- ">grep schauer passwd "Das ist nur eine Shell. Bedenklich waere, wenn Dein LILO /vmunix.el bootet." -- Kristian und Holger in de.comp.os.linux.misc