Package name duplication in Hierachical Libraries

Package name duplication in Hierachical Libraries

[Stuart Forster]

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?

I've only tried it on gnat 3.13p.

package A is
   procedure C;
end A;

with Text_IO;
package body A is
   procedure C is
   begin
      Text_IO.Put_Line("A.C");
   end C;
end A;

package B is
end B;

package B.A is
   procedure C;
end B.A;

with A;
with Text_IO;
package body B.A is
   procedure C is
   begin
      Text_IO.Put_Line("B.A.C");
      A.C;                                    -- Instead of calling A.C
calls B.A.C.
   end C;
end B.A;

with B.A;
procedure Test is
begin
   B.A.C;
end Test;

Re: Package name duplication in Hierachical Libraries

[Florian Weimer]

"Stuart Forster" <stuart.forster@baesystems.com> 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.

Re: Package name duplication in Hierachical Libraries

[Stephen Leake]

"Stuart Forster" <stuart.forster@baesystems.com> 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, the compiler is doing what you told it to do.

Within package "B", the name "A.C" refers to "B.A.C". To get the one
you want, use "Standard.A.C".

> <snip code> 

-- 
-- Stephe