[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Inheritance of Methods
- To: skeene@STONY-BROOK.SCRC.Symbolics.COM
- Subject: Re: Inheritance of Methods
- From: Masinter.pa@Xerox.COM
- Date: 22 Jan 87 10:59 PST
- Cc: common-lisp-object-system@SAIL.STANFORD.EDU
- In-reply-to: Sonya E. Keene <skeene@STONY-BROOK.SCRC.Symbolics.COM>'s message of Thu, 22 Jan 87 11:09 EST
What gets inherited is more than accessors and less than methods, that
is, a subclass inherits the accessors, since, in some sense, the
accessors "belong" to the class. We are reluctant to say that subclasses
inherit "methods" because a multi-method may not "belong" to any one
class, and the analogy of inheritance implies the analogy of possesion.
What is important is that behavior, reflected in the availability of
accessors and the participation in method lookup, is inherited. What do
you think of "Inheritance of Behavior" for a section title?