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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,a8985ede8fe3d111
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1994-10-18 15:44:40 PST
Path: 
 bga.com!news.sprintlink.net!howland.reston.ans.net!swiss.ans.net!cmcl2!thecourier.cims.nyu.edu!thecourier.cims.nyu.edu!nobody
From: dewar@cs.nyu.edu (Robert Dewar)
Newsgroups: comp.lang.ada
Subject: Re: Child packages
Date: 18 Oct 1994 15:09:25 -0400
Organization: Courant Institute of Mathematical Sciences
Message-ID: <3816h5$n3g@schonberg.cs.nyu.edu>
References: <1994Oct4.090807@di.epfl.ch> <37kanl$jfd@u.cc.utah.edu>
 	<EACHUS.94Oct17115240@spectre.mitre.org> <1994Oct18.103131@di.epfl.ch>
 <EACHUS.94Oct18093732@spectre.mitre.org>
NNTP-Posting-Host: schonberg.cs.nyu.edu
Date: 1994-10-18T15:09:25-04:00
List-Id: <comp.lang.ada>

One thing that should be emphasized about child packages (since some of
the posts of this thread have not been clear on this point) is that
child packages in no way change their parents. If you have a parent A,
and a child A.B, then if A.B does horrible things to the abstractions
in A, it still does not affect anyone who with's only package A. It is
only if package A.B is with'ed that the effects of the child are
noticable.