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
X-Google-Attributes: gid103376,public
From: Serge.Rybin@di.epfl.ch (Serge Rybin)
Subject: Re: Visibility of packages in child bodies...
Date: 1996/04/17
Message-ID: <4l2rfo$3l1@disunms.epfl.ch>#1/1
X-Deja-AN: 147971963
distribution: world
sender: rybin@lglsun7.epfl.ch (Serge Rybin)
references: <4l1uss$acu@goanna.cs.rmit.edu.au>
content-type: text/plain; charset=iso-8859-1
organization: Ecole Polytechnique F�d�rale de Lausanne
mime-version: 1.0
newsgroups: comp.lang.ada
Date: 1996-04-17T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <4l1uss$acu@goanna.cs.rmit.edu.au>, Dale Stanbrough <dale@goanna.cs.rmit.EDU.AU> writes:
:> 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.


But, for sure, it is possible to refer to STANDARD.useful.
And you can use the "local" renamings of STANDARD.useful instead of
(annoying) library level renaming.

Sergey Rybin