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,23e3ddd47450e30c X-Google-Attributes: gid103376,public From: stt@houdini.camb.inmet.com (Tucker Taft) Subject: Re: Ada 95 visibility question Date: 1997/09/25 Message-ID: #1/1 X-Deja-AN: 275643483 Sender: news@inmet.camb.inmet.com (USENET news) X-Nntp-Posting-Host: houdini.camb.inmet.com References: <60ear5$7hu$1@beauty.mda.ca> Organization: Intermetrics, Inc. Newsgroups: comp.lang.ada Date: 1997-09-25T00:00:00+00:00 List-Id: Bruce Link (bdl@mda.ca) wrote: : ... : Robert Duff cites 7.3.1 (no paragraph), but this does not seem to apply in : the way he intends it. Bob is right, but 7.3.1 is not exactly crystal clear on the topic. Slightly better is AI95-00157. The key thing to realize is that knowing anything about the grandparent of a derived type is irrelevant. All that matters is what characteristics of the immediate parent type are *visible* in the immediate scope of the derived type. In this case, because the parent type is defined in a sibling package, rather than an ancestor package, one only sees the public characteristics of the parent type, and even though you "know" more about the grandparent type, that is irrelevant. The only way to take advantage of what is known about a grandparent type is to convert to that grandparent type. : Bruce Link |Team OS/2 : bdl@mda.ca |Team Ada -- -Tucker Taft stt@inmet.com http://www.inmet.com/~stt/ Intermetrics, Inc. Burlington, MA USA