From: "Campbell, Rolf [SKY:1U32:EXCH]" <moscoop AT americasm01 DOT nt DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Prevent crash on free()
Date: Mon, 28 Feb 2000 14:36:13 -0500
Organization: Nortel Networks
Lines: 15
Message-ID: <38BACE2C.7052937E@americasm01.nt.com>
References: <89e5e3$8g1$1 AT cubacola DOT tninet DOT se> <89e72m$hpt$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <89e7oq$cmv$1 AT cubacola DOT tninet DOT se>
NNTP-Posting-Host: wmerh0tk.ca.nortel.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.72 [en] (X11; I; HP-UX B.10.20 9000/785)
X-Accept-Language: en
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Marcus wrote:

> Sorry but that's my attitude :)
> I do a library and I want a way to check if I can free the memory. Of course
> I can ignore that. But how fun would it be with memory leaks?

    Why would there be any question about whether the memory should be free'd?
Free it if you allocated it.
Don't if you didn't.

--
(\/) Rolf Campbell (\/)