[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Class redefinition and class-changed.
- To: Danny Bobrow <Bobrow.pa@XEROX.COM>
- Subject: Re: Class redefinition and class-changed.
- From: Patrick H Dussud <DUSSUD%Jenner%ti-csl.csnet@RELAY.CS.NET>
- Date: Fri, 24 Jul 87 15:11:33 CDT
- Cc: DUSSUD%Jenner%ti-csl.CSNet@RELAY.CS.NET, common-lisp-object-system@SAIL.STANFORD.EDU
- In-reply-to: Msg of 24 Jul 87 08:48 PDT from Danny Bobrow <Bobrow.firstname.lastname@example.org>
Date: 24 Jul 87 08:48 PDT
From: Danny Bobrow <Bobrow.email@example.com>
Subject: Re: Class redefinition and class-changed.
It doesn't have to guess. If the class changed method is defined before
any any method is called on an obsolete instance, it will be used.
Otherwise not. Hence users should define such class-changed methods
immediately (soon) after redefining the class.
In multiprocessing or interruptible environment, immediately is a weak
concept at best. You might get in a race condition with another
computation unit that touches instances. Furthermore, you can't prove
that some instances haven't been updated before you define the
changed-class method. How do you propose to solve this?