CL> You can only pass in an arbitrary environment if you call CL> MACROEXPAND or MACROEXPAND-1 directly. These functions allow an CL> environment to be passed so that programs that analyze CL code CL> (e.g. the compiler) can specify an environment other that the CL> global one. Even "worse": AFAIK, how the environment looks like, is an implementation detail (at least, I haven't found any example in the HyperSpec). -- --- http://www.coling.uni-freiburg.de/~schauer --- "Deine capslock und '!' Tasten klemmen." "Nee, ich habe eine Win95 Tastatur." -- Robin Socha und H.Wulff in de.comp.os.linux.misc