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,449b3383afc55069,start
X-Google-Attributes: gid103376,public
From: johnjohn@triceratops.com
Subject: Child package: private type and IO
Date: 1998/02/14
Message-ID: <6c2r0l$iic$1@madmax.keyway.net>#1/1
X-Deja-AN: 324916400
Organization: Keyway Internet Access 909-933-3650
Newsgroups: comp.lang.ada
Date: 1998-02-14T00:00:00+00:00
List-Id: <comp.lang.ada>


I'm trying to write two separate packages, one for a private
type and constructor, and the other an IO package.  House
rules. :(

The need, obviously, is for the IO package to be able to
access the private type internals, a feature which seems
to be supported via the child package system.  It's unclear
to me, however, exactly how a package is declared to be
a child of the original.

Picking up Skansholm's Ada From the Beginning, usually a pretty
good resource, is particularly emptly on package externals (file
extensions, for example).

Actually, now that I say that, Skansholm does have a reference
to naming a child package "PARENT_PKG.CHILD_NAME".

However, using this convention gets me the following compilation
error on the "with" declaration:  
file "parent_pkg-child_name.ads" not found

Any tips?  Any pointers to a better handling of child packages?

Thanks.

John