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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,76ec5d55630beb71 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-06-02 07:25:11 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.arcor-online.net!fu-berlin.de!uni-berlin.de!213.200.246.247!not-for-mail From: Vinzent Hoefler Newsgroups: comp.lang.ada Subject: Re: Ada 200X Date: Mon, 02 Jun 2003 16:23:50 +0200 Organization: JeLlyFish software Message-ID: References: <3EDAD07A.3010200@attbi.com> <1054562949.551399@master.nyc.kbcfp.com> NNTP-Posting-Host: 213.200.246.247 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: fu-berlin.de 1054563908 9164757 213.200.246.247 (16 [175126]) X-Newsreader: Forte Agent 1.8/32.548 Xref: archiver1.google.com comp.lang.ada:38348 Date: 2003-06-02T16:23:50+02:00 List-Id: Hyman Rosen wrote: >Larry Kilgallen wrote: >> The lack of a construct to specify "corresponding method of ancestor" >> seems to me to be what breaks information hiding. > >Can't you just do a view conversion to the ancestor type >and call the method? Yes, but who is the ancestor? You always have to look for that. I guess, Larry means something like |inherited method (...); instead of the specific |ancestor.method (...) call in Turbo (Object?) Pascal. >That's not dispatching, so you'll >call the method defined for the ancestor type. Yeah, right. But it would be easier to just write the equivalent to $WHATEVER_THE_CURRENT_ANCESTOR is instead of specifying it each time. Sometimes the object hierarchy might change a little bit. Vinzent.