From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,899484222880ae7c
X-Google-Attributes: gid103376,public
From: kilgallen@eisner.decus.org (Larry Kilgallen)
Subject: Re: preventing inheritance
Date: 1996/12/17
Message-ID: <1996Dec17.080010.1@eisner>#1/1
X-Deja-AN: 204542680
x-nntp-posting-host: eisner.decus.org
references: <32B22CDC.3FE4@bix.com> <32B5A234.947@watson.ibm.com>
 <32B640FC.D30@bix.com> <32B64298.3CC5@bix.com>
x-nntp-posting-user: KILGALLEN
x-trace: 850827615/6752
organization: LJK Software
newsgroups: comp.lang.ada
Date: 1996-12-17T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <32B64298.3CC5@bix.com>, Tom Moran <tmoran@bix.com> writes:
> The real problem is that U really 'is a' T, it's just that MS does not
> give a way to implement a particular operation on objects of type U.
> It is not satisfying to simply say 'well, I guess U's aren't T's after
> all'.

Inheritance capabilities in a language provide compiler enforcement
of an orderly set of relationships.  We tend to value them because
they detect cases where the set of relationships we had in mind is
not orderly.  Unfortunately they also detect cases where the lack
of orderliness originated outside our sphere of influence.

Larry Kilgallen