From: Pascal B. <pj...@in...> - 2006-12-01 04:35:42
|
Berki Lukacs Tamas writes: >=20 > The following form: >=20 > (defun foo (&whole whole) 42) >=20 > Yields this answer on SBCL 0.9.14 and 1.0 (on Ubuntu 6.10 without SLIME= , > simple using the CLI): >=20 > debugger invoked on a SB-INT:BUG in thread #<THREAD "initial thread" > {A8154E9}>: >=20 > unknown LAMBDA-LIST-KEYWORD in lambda list: &WHOLE.=20 As expected. Why would you want to use a MACRO lambda list with deFUN? > This is probably a bug in SBCL itself.=20 No, this is mandated by the CL specifications. DEFUN uses ordinary lambda lists, not macro lambda lists. http://www.lispworks.com/documentation/HyperSpec/Body/03_da.htm =20 > The result is the same with &environment, although any other symbol > beginning with & works. The other symbols beginning with & are normal symbols. (That is, all the symbols that are not in LAMBDA-LIST-KEYWORDS). &FOO isn't even in the CL package! --=20 __Pascal Bourguignon__ http://www.informatimago.com/ ATTENTION: Despite any other listing of product contents found herein, the consumer is advised that, in actuality, this product consists of 99.9999999999% empty space. |