Re: Uninitialized "out" parameters

[bobduff@world.std.com (Robert A Duff)]

In article <dewar.838132465@schonberg>, Robert Dewar <dewar@cs.nyu.edu> wrote:
>I have an array of 2 gigabytes in an allocate-on-demand environment. I use
>this as a sparse hash table, but it is critical that only pages that are
>actually used get referenced, so it is out of the question to initialize
>the table.

I don't understand your example.  A hash table normally has an operation
for determining whether a given item is in the table, and this operation
is going to have to read pages that have never been written.  So, the
allocate-on-demand feature needs to zero out pages upon allocation, or
somehow set them to a well-defined value.

If I write:

    Table: Giant_Array := (others => null);

I believe the DEC Ada compiler on VAX/VMS will notice that null is zero,
and not actually zero out the whole array, but rely on the fact that the
operating system will zero out each page as it is allocated.  Is this
not true?  Are there any other Ada compilers smart enough to do this
(presuming the underlying OS supports allocate-on-demand)?  (Actually,
if it's an array of pointers, it will be initialized to null without the
aggregate -- we had a big argument here a while back about that.)

By the way, a few months ago I wrote a program, and it was running too
slow, so I profiled it, and found that it was spending a huge percentage
of its time setting access values to their default null value, in cases
where I could prove this to be unnecessary.  I actually resorted to a
pretty ugly hack to get the compiler to quit generating those
initializations.  I was using GNAT on Linux.

- Bob