[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
another question about defmacro lambda lists
- To: Sandra J Loosemore <sandra%utah-orion@UTAH-CS.ARPA>, common-lisp@sail.stanford.edu
- Subject: another question about defmacro lambda lists
- From: David C. Plummer <DCP@QUABBIN.SCRC.Symbolics.COM>
- Date: Fri, 23 Jan 87 15:10 EST
- In-reply-to: <8701231927.AA25049@utah-orion.ARPA>
Date: Fri, 23 Jan 87 12:27:25 MST
From: sandra%utah-orion@utah-cs.arpa (Sandra J Loosemore)
Does it make sense for nested lambda lists in a defmacro to contain things
like &environment?
No, it doesn't make sense. There is only one environment (the one in
which the macro is being expanded in). (Nor can it be destructured.)
CLtL does not say whether the non-top-level lambda lists
should be ordinary function lambda lists or whether they can use the extended
syntax.
I almost couldn't find &environment because of a "publishing" glitch!!
The last paragraph on page 145 is supposed to have &environment next to
it, but doesn't. Indeed, the spec should be explicit about what may
appear in nested lambda lists.