From: Georg Bauhaus <bauhaus@futureapps.de>
Subject: Re: exception access violation
Date: Wed, 15 Nov 2006 10:52:10 +0100
Date: 2006-11-15T11:49:28+01:00 [thread overview]
Message-ID: <1163584330.6500.6.camel@localhost.localdomain> (raw)
In-Reply-To: <4s06i8FsekphU1@mid.individual.net>
On Wed, 2006-11-15 at 10:58 +0100, Alex R. Mosteo wrote:
> However, if you're managing large data structures (over 4MB in size), I'd go
> for a heap-based solution using controlled types. In my experience, abusing
> the stack is a source of headaches sooner or later (specially if you are
> doing something portable).
Why is using the heap + controlled for larger data structures
more portable than using the stack? I know that GNAT needs to
be talked into providing sufficient space on the stack.
You might be that running into this kind of stack trouble only
when you port from another compiler to GNAT?
Should the decision whether some object lives on the heap or on
the stack be based on compilers' support for dynamically sized
local data structures?
next prev parent reply other threads:[~2006-11-15 9:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 19:31 exception access violation Jade
2006-11-13 21:35 ` Georg Bauhaus
2006-11-14 9:09 ` Alex R. Mosteo
2006-11-14 19:34 ` Jade
2006-11-15 9:58 ` Alex R. Mosteo
2006-11-15 9:52 ` Georg Bauhaus [this message]
2006-11-15 13:32 ` Alex R. Mosteo
2006-11-15 23:43 ` Kevin K
-- strict thread matches above, loose matches on Subject: below --
2009-05-18 16:05 Exception_Access_Violation mhamel_98
2009-05-18 16:14 ` Exception_Access_Violation John B. Matthews
2009-05-19 7:23 ` Exception_Access_Violation Alex R. Mosteo
2009-05-20 15:30 ` Exception_Access_Violation mhamel_98
2009-05-22 14:34 ` Exception_Access_Violation Björn Persson
2009-05-22 15:17 ` Exception_Access_Violation Niklas Holsti
2009-05-22 16:38 ` Exception_Access_Violation Adam Beneschan
2001-12-07 12:41 exception access violation Cousins, Jeff
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox