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,8b8748382fcfacc1
X-Google-Attributes: gid103376,public
From: John Rusnak <john.j.rusnak@lmco.com>
Subject: Re: friend classes in ada95
Date: 2000/04/18
Message-ID: <38FCD3BA.AE2A0A50@lmco.com>#1/1
X-Deja-AN: 612863193
Content-Transfer-Encoding: 7bit
References: <38F6B617.34E216A7@emw.ericsson.se>
 <38F6D9F0.F0DE08E4@geocities.com> <8d7lqt$cgu$1@epos.tesco.net>
 <wcc8zygbioi.fsf@world.std.com> <38FBE174.9FCD06B7@mindspring.com>
 <38FC97AC.3968@li.net>
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii
Organization: Lockheed Martin Corporation
Mime-Version: 1.0
Newsgroups: comp.lang.ada
Date: 2000-04-18T00:00:00+00:00
List-Id: <comp.lang.ada>

I see!

So only the private part of a public child can access the private part
of its parent. I guess I never came across a situation where that was
necessary.

 This still represents a way to implement a friend-relationship in Ada,
though.  Although the public interface to a tagged type in a child
package cannot have visiblity into the parent, the implementation
defined in the body can.  This is usually what I find important on those
rare occasions when a "friend" is helpful.

-John