From:	broeker AT acp3bf DOT knirsch DOT de (Hans-Bernhard Broeker)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: freeing memory and exiting (safely)
Date:	23 Dec 1999 14:47:53 +0100
Organization:	RWTH Aachen, III. physikalisches Institut B
Lines:	20
Message-ID:	<83t969$ras@acp3bf.knirsch.de>
References:	<83ril4$4ua$1 AT portraits DOT wsisiz DOT edu DOT pl>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 945956875 10674 137.226.32.75 (23 Dec 1999 13:47:55 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	23 Dec 1999 13:47:55 GMT
X-Newsreader:	TIN [version 1.2 PL2]
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Chaos (chengin AT alpha DOT net DOT pl) wrote:

> My question is that if the prog reaches that "return 1" (synonim for error)
> does those buffers will be safely deallocated?

Yes. If not, it's a bug in your operating system, and there's nothing
you can do about _that_ (other than using a better OS).

> just want to exit safe from the program and deallocate it's memory without
> blocking it in later use.

Just terminate with 'exit(1);', and that's it.





-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -