From: "Chaos" <chengin AT alpha DOT net DOT pl>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: freeing memory and exiting (safely)
Date: Sun, 26 Dec 1999 15:33:11 +0100
Organization: Chaos Engine
Lines: 26
Message-ID: <848onq$rvo$2@portraits.wsisiz.edu.pl>
References: <83ril4$4ua$1 AT portraits DOT wsisiz DOT edu DOT pl> <rCe84.372$36 DOT 7194 AT carnaval DOT risq DOT qc DOT ca>
NNTP-Posting-Host: pe191.warszawa.ppp.tpnet.pl
X-Trace: portraits.wsisiz.edu.pl 946333242 28664 212.160.56.191 (27 Dec 1999 22:20:42 GMT)
X-Complaints-To: abuse AT news DOT wsisiz DOT edu DOT pl
NNTP-Posting-Date: 27 Dec 1999 22:20:42 GMT
X-Newsreader: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.1
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

>No. C or the std C library does not provide such facilities.
>When malloc()/realloc()/calloc() returns an error (NULL), it means
>there is not space left to allocate, you could free() some
>unused previously allocated buffers, do something else that does
>not need to allocate memory or exit();

I know that. In previously posts I was given specific answer. But thnx for
your mail also :-)

>If you reach that level, it's maybe time for you to rethink,
>your design and thight things up.

I agree. But anyway, I thank God for protected mode and its tones of
megabytes of ram ;-))

>--
>au revoir, alain
>----
>Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!!

Take care.
-=| Chaos |=-
e-mail:  chengin AT alpha DOT net DOT pl
              chengin AT polbox DOT com