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,start X-Google-Attributes: gid103376,public From: Stefan Folkesson Subject: friend classes in ada95 Date: 2000/04/14 Message-ID: <38F6B617.34E216A7@emw.ericsson.se>#1/1 X-Deja-AN: 610993000 Content-Transfer-Encoding: 7bit X-Accept-Language: en Content-Type: text/plain; charset=us-ascii X-Trace: news.emw.ericsson.se 955692578 136.225.182.62 (Fri, 14 Apr 2000 08:09:38 MET DST) Organization: Ericsson Microwave Systems AB MIME-Version: 1.0 NNTP-Posting-Date: Fri, 14 Apr 2000 08:09:38 MET DST Newsgroups: comp.lang.ada Date: 2000-04-14T00:00:00+00:00 List-Id: In ADA95, is there a way to make the private part of one class accessable from another (see friend classes in C++)? The reason I wonder this is because I want to apply the 'Iterator Pattern' in my design. This demands that the Iterator object can access the attributes of the Aggregate object. Is this possible? Is there a pragma to supress the access check or do I have to declare the attributes of the Aggregate class in the public part of the specification. /Stefan