Re: Problem with instantiating generic procedure

[Florian Weimer <fw@s.netic.de>]

Robert Dewar <robert_dewar@my-deja.com> writes:

> But the name space pollution is a minimal problem, because it
> occurs only in private parts or in package bodies, not in
> package specs.

Thanks, I wasn't aware of this.

> I would guess this is in practice of minimal importance. In all
> the use of GNAT so far, this issue has never come up, so it is
> certainly not something that many people expect to be there!

This seems to be case for this specific use of pragma Import as well,
because GNAT 3.11p generates bad code for your example. ;) (A call to
procedure q (with or without an integer argument) results in a `call q'
instruction in both cases, which is certainly wrong.)

> package p is
>    procedure q;
>    procedure q (x : integer);
> private
>    procedure q_no_args renames q;
>    procedure q_int_arg (x : integer) renames q;
> 
>    pragma Import (C, q_no_args);
>    pragma Import (C, q_int_arg);
> 
> end p;

The renaming declaration are `in the wrong direction', I guess.
Something like this is required instead:

package p is
   procedure q;
   procedure q (x : integer);
private
   procedure q_no_args;
   procedure q_int_arg (x : integer);

   pragma Import (C, q_no_args);
   pragma Import (C, q_int_arg);

   procedure q renames q_no_args;
   procedure q (x : integer) renames q_int_arg;
end p;