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-22 17:33:08 PST Path: bga.com!news.sprintlink.net!howland.reston.ans.net!gatech!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: 19 Oct 1994 19:13:16 -0400 Organization: Courant Institute of Mathematical Sciences Message-ID: <38496c$1l1@gnat.cs.nyu.edu> References: <1994Oct4.090807@di.epfl.ch> <37kanl$jfd@u.cc.utah.edu> <1994Oct18.103131@di.epfl.ch> <3816h5$n3g@schonberg.cs.nyu.edu> <383h86$12ip@watnews1.watson.ibm.com> NNTP-Posting-Host: gnat.cs.nyu.edu Date: 1994-10-19T19:13:16-04:00 List-Id: Norman, there is still a big difference between modifying the text of a package and adding a child, much to big for tantamout :-) The big difference is that if you modify the text of a package you can blow up existing clients of that package in different programs. If you write a child, it is completely separate, and affects on programs that use the child, so the level of access controls needed is quite different. a given program may want to lock out any additional child units, and another program may wish to allow them, but neither could permit the mucking with a shared package's text.