Re: Renaming subprogram and default_expression

[Larry Hazel <lhhazel@otelco.net>]

Florian Weimer wrote:
> 
> "Alexander Boucke" <alexb@lufmech.rwth-aachen.de> writes:
> 
> > Type roman is range 1..3999; is defined in strings edit.ads Note,
> > that gnat3.14p does not complain about the preset values for the
> > booelan arguments, only for the new integer type. If I comment these
> > default values, the program compiles. This seems to be the same
> > error as in the short testprog. starting this thread: A new
> > integer-type was used there, too.
> 
> You can eliminate the integer type.  The minimal test case for GCC 3.1
> is:
> 
> procedure Defaults is
> 
>    procedure Original (X : Integer);
>    procedure Renamed (X : Integer := -1);
> 
>    procedure Renamed (X : Integer := -1)
>      renames Original;
> 
>    procedure Original (X : Integer) is
>    begin
>       null;
>    end Original;
> 
> begin
>    null;
> end Defaults;
> 
> (I wouldn't have thought that such basic things are broken, that's why
> I had not tried the default Integer type.)
> 
> I don't know why the bug doesn't occur with string types.  Oh well.

If you remove the declaration of Renamed and just leave the renames statement,
there is no error.  And here there is no need for the declaration.  However, if
you make it a package:

package Defaults is

   procedure Original (X : Integer);
   procedure Renamed (X : Integer := -1);

private

   procedure Renamed (X : Integer := -1)
     renames Original;
     
end Defaults;

the declaration is needed, and you get the error.  Looks like a bug.

Larry