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:40:36 -0500
Organization:	Nortel Networks
Lines:	21
Message-ID:	<38BACF34.A7DC20B0@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> <89ecto$jum$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <89ee3g$8pf$1 AT zingo DOT tninet DOT se>
NNTP-Posting-Host:	wmerh0tk.ca.nortel.com
Mime-Version:	1.0
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:

> Is it impossible to know if the function have been called this way
> func ("...");
> or
> char* a = malloc(10);
> func (a);
> ?
> Do you understand what I mean? And what is YAMD?

    In general, I believe a good policy is:
A library (or class, etc) shouldn't free memory it didn't allocate.

I don't think your 'func' function should be free'ing any memory it doesn't
allocate itself.

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

- Raw text -