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,a236155f75e58a6d,start
X-Google-Attributes: gid103376,public
From: Dale Stanbrough <dale@goanna.cs.rmit.EDU.AU>
Subject: Visibility of packages in child bodies...
Date: 1996/04/17
Message-ID: <4l1uss$acu@goanna.cs.rmit.edu.au>#1/1
X-Deja-AN: 147923252
distribution: world
content-type: text/plain; charset=ISO-8859-1
x-xxmessage-id: <AD9ABCCF64011B17@obibicut.cs.rmit.edu.au>
organization: Royal Melbourne Institute of Technology
mime-version: 1.0
newsgroups: comp.lang.ada
Date: 1996-04-17T00:00:00+00:00
List-Id: <comp.lang.ada>

If a series of library packages are created as...

	package useful is...
	
	package a is...
	
	package a.useful is...
	
then in the package body of a.useful is it possible to
refer to package "useful" without using a library level renaming?

e.g. in the following...

	with useful;
	
	package body a.useful is...
	
package "useful" is not directly visible.


The apparent solution...

	with useful;
	package useful_renaming_because_of_collision renames useful;
	
	
	with useful_renaming_because_of_collision;
	
	pacakge body a.useful is...
	
seems a bit annoying, in that a new library entry has to be created.

Dale