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,b6d543b1cb62702
X-Google-Attributes: gid103376,public
From: Christoph Grein <christoph.grein@eurocopter.de>
Subject: package child question
Date: 2000/02/08
Message-ID: <200002080707.IAA16433@bulgaria.otn.eurocopter.de>#1/1
X-Deja-AN: 584487086
To: comp.lang.ada@ada.eu.org
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: F16g3t68HNEVEDo0ax2+Tg==
X-Complaints-To: usenet@enst.fr
X-Trace: menuisier.enst.fr 950263919 17590 137.194.161.2 (11 Feb 2000 10:11:59
 GMT)
Organization: ENST, France
X-BeenThere: comp.lang.ada@ada.eu.org
Mime-Version: 1.0
Reply-To: comp.lang.ada@ada.eu.org
NNTP-Posting-Date: 11 Feb 2000 10:11:59 GMT
Newsgroups: comp.lang.ada
Date: 2000-02-11T10:11:59+00:00
List-Id: <comp.lang.ada>

Matthew Heaney has pointed out the cause of your problem.

Apart from renaming, another solution is possible. Remember that any library
unit is supposed to be a child of Standard, so you might write

with A.B;
package body B.A is  -- this A hides the imported one

begin
   declare
      use Standard.A.B;  -- qualification makes it accessible again
   begin
      null;
   end;
end B.A;