From: NiGHTS <nights@unku.us>
Subject: Mission-Critical Design: Ada.Unchecked_Deallocation vs Garbage Collection
Date: Thu, 17 Jul 2014 23:17:48 -0700 (PDT)
Date: 2014-07-17T23:17:48-07:00 [thread overview]
Message-ID: <de300b26-804d-4c9a-8aea-e840160b735d@googlegroups.com> (raw)
In mission-critical design applications, do they favor garbage collectors or the unchecked deallocation?
The dangling pointer thing is definitely a problem I've had to deal with in complex C programs that I have debugged. But I can also see how having an unpredictable pool of memory hanging over the program could be a problem as well. I suppose this question is highly dependant on the application and target.
What are your thoughts on this? When is it better to use garbage collection and when is it better to use classic new & delete memory management when a life may be on the line?
next reply other threads:[~2014-07-18 6:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 6:17 NiGHTS [this message]
2014-07-18 6:25 ` Mission-Critical Design: Ada.Unchecked_Deallocation vs Garbage Collection Jeffrey Carter
2014-07-18 7:51 ` J-P. Rosen
2014-07-19 9:07 ` Pascal Obry
2014-07-18 12:41 ` Dennis Lee Bieber
2014-07-23 22:07 ` Robert A Duff
2014-07-24 1:00 ` Dennis Lee Bieber
2014-07-24 6:52 ` Simon Wright
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox