[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Inheritance of Slots
- To: Moon@STONY-BROOK.SCRC.Symbolics.COM
- Subject: Re: Inheritance of Slots
- From: Danny Bobrow <Bobrow.pa@Xerox.COM>
- Date: 10 Feb 87 10:38 PST
- Cc: common-lisp-object-system@SAIL.STANFORD.EDU
- In-reply-to: David A. Moon <Moon@STONY-BROOK.SCRC.Symbolics.COM>'s message of Tue, 10 Feb 87 12:32 EST
- Sender: Bobrow.pa@Xerox.COM
I read the current document last night and was appalled at the
complexity of the rules that were used to explain the inheritance of the
characterisics of slot-descriptions. I also realized that accessors
and readers MUST be inherited. A new method need not be built for every
class if the implementation guarantees that the method inherited still
works. But whenever there is a change of the :allocation
characteristic, every accessor and reader in the inheritance chain must
have a new method created for it.
danny