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 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,8b3d7c27160f8353 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-01-02 04:54:11 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!news-was.dfn.de!news-lei1.dfn.de!news-nue1.dfn.de!news-han1.dfn.de!news.fh-hannover.de!news.cid.net!news.enyo.de!news1.enyo.de!not-for-mail From: Florian Weimer Newsgroups: comp.lang.ada Subject: Re: Package name duplication in Hierachical Libraries Date: Wed, 02 Jan 2002 13:52:36 +0100 Organization: Enyo's not your organization Message-ID: <87g05o3off.fsf@deneb.enyo.de> References: <3c32e619$1@pull.gecm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cancel-Lock: sha1:7P5ODjZjp7yeRuHCNU0UC91jZnY= Xref: archiver1.google.com comp.lang.ada:18442 Date: 2002-01-02T13:52:36+01:00 List-Id: "Stuart Forster" writes: > I have a problem with duplicated package names in hierarchical libraries. > > The example below results in an infinite recursion of B.A.C where I was > hoping for > >>Test > B.A.C > A.C >> > > Is this the correct behaviour? Yes, I think so. You can use Standard.A.C to refer to the other package.