Re: memory leakages with Ada?

["Marin David Condic" <dont.bother.mcondic.auntie.spam@[acm.org>]

Clearly, there will be stylistic differences depending on the methodology
employed in designing the program. Object Oriented stuff tends to deal with
things easier if you have pointers to things. Hence OOP stuff in Ada would
have more dynamic allocation than a functional approach or some other
strategy. I'll concede that point.

But being an active C programmer at the moment (and sadly shaking my head
and telling my associates "It doesn't have to be this way..." as we spend
months debugging and chasing among other typical C problems - memory leaks)
I find myself having to deal with dynamically allocated data in the most
mundane of circumstances - often because that's just what many of the
library calls return to you. (The libraries we are using - not necessarily
the standard C libraries.) You just find yourself doing mallocs (Bumper
sticker: "Free The Mallocs!") all over the place and referencing things with
pointers all the time just because that's the way C wants you to do it. Ada
doesn't make it necessary to use dynamic allocation or pointers to do
mundane tasks.

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com
Web:      http://www.mcondic.com/


"John McCabe" <john.mccabe@emrad.ns.com> wrote in message
news:3c91bfa3.1987537@news.demon.co.uk...
>
> I'm not convinced this comment is 100% valid, from having worked on
> large scale Object-Oriented Ada projects over the last 3 years or so
> where there has been significant (if not huge) amounts of dynamic
> allocation. It is at least partially true in that you can often
> restructure your code to avoid dynamic allocation, but...