comp.lang.ada
 help / color / mirror / Atom feed
From: gautier_niouzes@hotmail.com
Subject: Re: Why people wants to complicate code with Ada.Unchecked_Deallocation?
Date: 27 Jul 2006 04:54:48 -0700
Date: 2006-07-27T04:54:48-07:00	[thread overview]
Message-ID: <1154001288.534738.48180@i42g2000cwa.googlegroups.com> (raw)
In-Reply-To: 44c7c3d3$0$47958$4fafbaef@reader3.news.tin.it

fabio:
[...]
> Does it mean that, for safety sake, programmers should not care about memory
> consumption?
>
> I am not sure I can agree with that. I've been tought that any "malloc"
> and "new" must be followed by "free" and "delete".
>
> What do you think about this issue?

I'm rather of your opinion.
If you start leaving memory leaks all around units it can become very
annoying as the projects grow and age.
You cannot predict if the target system will be plentiful enough to
absorb possible leaks or how long or on which input data size the
program will run.
It can happen that the pollution size at time t is a power of t times a
power of input data units or something like that...

IMHO it's a fully cultural problem.
Some people have tendency to say "just buy more storage, it's cheap",
other prefer to keep control of the rubbish...

Gautier
______________________________________________________________
Ada programming -- http://www.mysunrise.ch/users/gdm/gsoft.htm

NB: For a direct answer, e-mail address on the Web site!




      parent reply	other threads:[~2006-07-27 11:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-26 19:34 Why people wants to complicate code with Ada.Unchecked_Deallocation? fabio de francesco
2006-07-26 19:51 ` Georg Bauhaus
2006-07-26 19:56 ` Simon Wright
2006-07-26 21:28 ` Jeffrey R. Carter
2006-07-27 15:49   ` adaworks
2006-07-27 19:11     ` Jeffrey R. Carter
2006-07-27 22:52     ` Simon Wright
2006-07-27 23:28       ` Robert A Duff
2006-07-27  0:07 ` Peter C. Chapin
2006-07-27 11:54 ` gautier_niouzes [this message]
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox