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.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 border2.nntp.dca1.giganews.com!nntp.giganews.com!newspeer1.nac.net!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!news.stack.nl!aioe.org!.POSTED!not-for-mail
From: Victor Porton <porton@narod.ru>
Newsgroups: comp.lang.ada
Subject: Parent/child dependencies and internal library units
Date: Wed, 23 Jul 2014 19:20:27 +0300
Organization: Aioe.org NNTP Server
Message-ID: <lqoncd$ue7$1@speranza.aioe.org>
NNTP-Posting-Host: rFX7cZOSaeuGGZI2vwQTaQ.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7Bit
X-Complaints-To: abuse@aioe.org
User-Agent: KNode/4.12.4
X-Notice: Filtered by postfilter v. 0.8.2
Xref: number.nntp.dca.giganews.com comp.lang.ada:187807
Date: 2014-07-23T19:20:27+03:00
List-Id: <comp.lang.ada>

I noticed that child units depend on their parents.

As such making parent dependent on a child makes a dependency loop.

Before noting this feature of Ada language, I thought parent units could be 
implemented based on their child units, but that does not work, because 
making parents dependent on children is a circular dependency.

So, my question:

What is a good way to create "internal" or "implementation" units for a 
unit? Should I create a *.Internal.* hierarchy of packages?

-- 
Victor Porton - http://portonvictor.org