From: Rod Kay <rodakay@internode.on.net>
Subject: Re: GNAT: Why does a large 'new' allocation blow the stack when an initialiser is present ?
Date: Fri, 1 Nov 2013 04:23:46 -0700 (PDT)
Date: 2013-11-01T04:23:46-07:00 [thread overview]
Message-ID: <4c0ed099-c746-406e-9f04-1623fa0655dd@googlegroups.com> (raw)
In-Reply-To: <lyk3gsse68.fsf@pushface.org>
On Friday, 1 November 2013 19:45:51 UTC+11, Simon Wright wrote:
>
> I'm not sure what "=> <>" is expected to do when there's no default
>
> value; I added "with Default_Component_Value => 42" to Integer_Array,
>
> and The_Array_1 (0) was 42 but The_Array_2 (1) was unchanged at 0!
Howdy,
Yes, somewhat odd. I'd thought (well, assumed) that if <> was used and no default value exists, then no initialisation takes place.
I also tried ...
:= new Integer_array' (1 .. 10_000_000 => 5);
... tho with no change in the result.
next prev parent reply other threads:[~2013-11-01 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 2:49 GNAT: Why does a large 'new' allocation blow the stack when an initialiser is present ? Rod Kay
2013-11-01 8:45 ` Simon Wright
2013-11-01 11:23 ` Rod Kay [this message]
2013-11-01 15:04 ` Georg Bauhaus
2013-11-01 10:19 ` sbelmont700
2013-11-01 11:28 ` Rod Kay
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox