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=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,b1f194b75ae020e4
X-Google-Attributes: gid103376,public
From: ncohen@watson.ibm.com (Norman H. Cohen)
Subject: Re: children
Date: 1995/03/27
Message-ID: <3l6p9s$12kj@watnews1.watson.ibm.com>#1/1
X-Deja-AN: 100540725
distribution: world
references: <3kv64j$1fhh@info4.rus.uni-stuttgart.de>
organization: IBM T.J. Watson Research Center
reply-to: ncohen@watson.ibm.com
newsgroups: comp.lang.ada
Date: 1995-03-27T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <3kv64j$1fhh@info4.rus.uni-stuttgart.de>,
ucaa2385@alpha1.csv.ica.uni-stuttgart.de (Peter Hermann) quotes Robert
Eachus as follows: 

|> ea: 
|>    Good point.  If the compiler is detecting illegitimate children, it
|> could also warn of any violation of good OO and SE principles, by that
|> child.  Let's see...I'd want a warning for any direct assignments to
|> variables in the body or the private part, and any overriding of
|> dispatching operations for types declared in the parent.  Anything
|> else?

What I really want is something I can't have:  Detection of a child
manipulating the representation of a private type in a way that violates
the representation invariants that the parent's author had in mind (and
probably forgot to document :-) ).

--
Norman H. Cohen    ncohen@watson.ibm.com