[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
INITIALIZE-INSTANCE &allow-other-keys
- To: clisp-list@ma2s2.mathematik.uni-karlsruhe.de
- Subject: INITIALIZE-INSTANCE &allow-other-keys
- From: Matthias Lindner <matthias@intellektik.informatik.th-darmstadt.de>
- Date: Sat, 16 Aug 1997 00:48:54 +0200
- Reply-to: matthias@intellektik.informatik.th-darmstadt.de
Hi,
it's me again still in trouble with CLISP's built-in CLOS.
What am I doing wrong here:
% clisp -q
> (defclass <C> () ())
#<STANDARD-CLASS <C>>
> (defmethod INITIALIZE-INSTANCE :after ((c <C>) &rest initargs
&key &allow-other-keys)
(print initargs))
WARNING:
The generic function #<GENERIC-FUNCTION INITIALIZE-INSTANCE> is being modified, but has already been called.
#<STANDARD-METHOD :AFTER (#<STANDARD-CLASS <C>>)>
> (make-instance '<c> :key 'val)
*** - illegal keyword/value pair :KEY, VAL in argument list. The allowed keywords are NIL
1. Break>
Is there a way to make INITIALIZE-INSTANCE recognize the
&allow-other-keys keyword?
--Matthias
------------------------------------------------------------------------------
Matthias Lindner
Wilhelm-Leuschner-Str.46
64293 Darmstadt
Germany
TEL: +49 6151 22071
NET: matthias@intellektik.informatik.th-darmstadt.de
WWW: http://aida.intellektik.informatik.th-darmstadt.de/~matthias/
------------------------------------------------------------------------------