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,FREEMAIL_FROM,
	INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,6161bc9aa025a9a3
X-Google-Attributes: gid103376,public
From: jamess1889@aol.com (JamesS1889)
Subject: Re: Subunits of packages vs. subunits of subprograms
Date: 1996/07/24
Message-ID: <4t50je$k5j@newsbf02.news.aol.com>#1/1
X-Deja-AN: 169906887
sender: root@newsbf02.news.aol.com
references: <31EA9976.5CD6@csehp3.mdc.com>
organization: America Online, Inc. (1-800-827-6364)
newsgroups: comp.lang.ada
Date: 1996-07-24T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <DuwKL6.Lsx@world.std.com>, bobduff@world.std.com (Robert A
Duff) writes:

>Library units (i.e. child units) can be procedures, too.

Dohh!!!!!  I didn't know that.  Well, then I guess Robert's answer makes
more sense.  Of course, the visibility is still at the end of the package,
not somewhere in the middle.  I guess as long as you declare specs for all
internal subprograms, there's really no reason not to make them child
units.

James Squire                                      
mailto:ja_squire@csehp3.mdc.com
MDA Avionics Tools & Processes
McDonnell Douglas Aerospace              http://www.mdc.com
Opinions expressed here are my own and NOT my company's
"Only one Earth Captain has ever survived battle with a Minbari fleet.  He
is behind me.
You are in front of me.  If you value your lives, be somewhere else!"
           -- Delenn, "Severed Dreams"