Re: Compiler default initialization of array types

["Matthew Heaney" <mheaney@on2.com>]

"Robert A Duff" <bobduff@shell01.TheWorld.com> wrote in message
news:wcc3cr4vcti.fsf@shell01.TheWorld.com...
>
> I have written code where there were lots of giant arrays of pointers,
> inside a record with another component indicating how many are valid.
> Something like:
>
>     type T is
>         record
>             Last: Natural := 0;
>             Pointers: Pointer_Array(1..Big_Number);
>
> Typically, objects of type T would use just a few pointers -- like Last
> might be 3 or 4, but very unusual for it to be 1000 or 1_000_000.
>
> It turned out that initializing all those unused pointers to null was a
> serious performance problem.  So I cheated: I declared the array as an
> array of integers (where the integer type was chosen to be the same size
> as a pointer), and used unchecked_conversion.

I've been thinking about this same issue while writing the Charles vector
type.  The STL plays tricks like you mention above, but it's not obvious how
to do this in Ada (portably, anyway).

One possibility is to declare a special storage pool type that works off the
internal array, and return the address of the array component that needs
initialization or finalization.  This would give you the rough equivalent of
placement new and explicit dtor invokation.

Something like this?

generic
   type Element_Type is private;
package GP is
...
private
   subtype Component_Subtype is
      Storage_Array (1 .. Element_Type'Max_Size_In_Storage_Elements);

   type Element_Array is
     array (Positive range <>) of aliased Component_Subtype;
...

Hmmm, that just might work.  Any possibility that
Max_Size_In_Storage_Elements will return a "large" value, even for a generic
actual type that is definite?

The only issue is that a storage pool is limited, which would make the
container type containing the pool limited too.  Maybe you could declare a
pool object in the body, but then you'd loose Preelaborate categorization,
and probably have to start worrying about synchronization issues.  Oh, the
joys of library design....