[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Class redefinition and class-changed.
- To: DUSSUD%Jenner%ti-csl.CSNet@relay.cs.net
- Subject: Re: Class redefinition and class-changed.
- From: Danny Bobrow <Bobrow.pa@Xerox.COM>
- Date: 23 Jul 87 19:41 PDT
- Cc: Bobrow.pa@Xerox.COM, common-lisp-object-system@SAIL.STANFORD.EDU
- In-reply-to: Patrick H Dussud <DUSSUD%Jenner@ti-csl.CSNET>'s message of Fri, 10 Jul 87 10:00:21 CDT
- Sender: Bobrow.pa@Xerox.COM
The necessary and sufficient condition for this is to
be able to get hold of an obsolete version of a class.
I don't agree. We said in chapter 1 that the updating of the
instances is done at an implementation-dependent time.
I agree that your arguments imply your conclusion. I think however,
that it would be better to say that "updating of the
instances is done at an implementation-dependent time sometime after the
class is redefined." Since this is really an environment support
feature, I think we should specify that it will not occur before the
first method on an obsolete instance is called.