Re: why is there an initargs arument for update-instance-for-redefined-class

In article
<12500bd7-1c82-4b0d-9f04-29e192592323@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
jimka <jimka@xxxxxxxxx> wrote:

As far as the MOP is concerned, having the initargs available would
allow
methods on subclasses of standard-object to call update-instance-for-
redefined-class
with a non-nil initargs. An example would be enlightening.

However, it seems that as far as standard-object is concerned, the
initargs
is useless on update-instance-for-redefined-class.

-jim

You have seen my remark?

Somebody defines :

(defmethod update-instance-for-redefined-class :around ( ...)
(call-next-method ... some-initargs ...))


The generic function will be called by the system updating
instances on class redefinition.
The :around method runs and supplies the initargs.

So:

* the user usually does not call this function
* the system calls it on redefition without initargs
* the around method is a way to introduce the initargs

--
http://lispm.dyndns.org/
.