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,772ae8afc5db35f2 X-Google-Attributes: gid103376,public From: tmoran@bix.com (Tom Moran) Subject: Re: Can't export object of private type Date: 1999/03/02 Message-ID: <36dba095.13738466@news.pacbell.net>#1/1 X-Deja-AN: 450298372 References: <7b1k4h$13k6@news3.newsguy.com> <36daf246.1947172@news.pacbell.net> <36db6723.31869063@news.pacbell.net> X-Complaints-To: abuse@pacbell.net X-Trace: typhoon-sf.pbi.net 920363494 206.170.2.72 (Tue, 02 Mar 1999 00:31:34 PDT) Organization: SBC Internet Services NNTP-Posting-Date: Tue, 02 Mar 1999 00:31:34 PDT Newsgroups: comp.lang.ada Date: 1999-03-02T00:00:00+00:00 List-Id: >If there is a derived type, it's within the package hierarchy: >package P is > type T (<>) is abstract tagged limited private; But what about with P; package Q is type Son_Of_T is new P.T with ... Or does the original question *only* refer to >package P.C is > type NT is new T with private; In which case, why even have T in the public part of P? It could be in the private part, where it's visible to P.C, and not visible to 'outsiders'. If you restrict T to being extended only in children of P, then it can be private, and the original question disappears.