Re: This can't be done in Ada...or?

["Per Lindquist" <commander@death-star.com>]

Robert A Duff wrote:
> No, instantiation is a compile-time concept.  I'm not sure what
> it would mean to delay it until run time.
>
> The issue here is the cost of running the elaboration code of the
> instance.  Theoretically, the compiler could optimize it away in this
> case, but I don't think any Ada compilers are that smart.  The only
> way to know for sure is to try it.
>
> This Reflection package has a bunch of string manipulation code,
> and if you instantiate it in a procedure, it will happen
> every time that procedure is called (unless the compiler
> is smarter than I think it is).  This could indeed be very
> costly.

I can now confirm that the Reflection package, in our case, indeed
causes considerable overhead compared to hardcoded constants.

The test consisted of 1_000_000 calls to procedure Q in either package
P1 or P2:

package body P1 is
  procedure Q is
    package Reflect is new PragmARC.Reflection;
  begin
    Dummy := Dummy + 1;
  end;
end P1;

package body P2 is
  procedure Q is
    Subprogram_Name : constant String := "Q";
  begin
    Dummy := Dummy + 1;
  end;
end P2;

(I'm aware that Reflect.Unit_Name is longer ("P1.Q") than
Subprogram_NAme ("Q") but this test is relevant in our case.)

I tested on a Sun (Solaris) machine using the GNAT compiler and on a
PowerPC (Integrity) using GreenHill's Ada compiler.

There was really no need for an accurate time measurement since the
difference was large on both platforms. The constant test finished
immediately and the Reflection test took several seconds.

Optimization flags (GNAT only) didn't do much difference.

So although PragmARC.Reflection offers very nice features we cannot use
it in our particular system.

Thanks for your help!

/PerL