delorie.com/archives/browse.cgi | search |
Message-ID: | <32D4B22D.54F9@post.comstar.ru> |
Date: | Thu, 09 Jan 1997 11:54:05 +0300 |
From: | Dim Zegebart <zager AT post DOT comstar DOT ru> |
Reply-To: | zager AT post DOT comstar DOT ru |
Organization: | Comstar Ltd. |
MIME-Version: | 1.0 |
To: | Serge Golovin <res AT marstu DOT mari DOT su> |
CC: | DJGPP Mail List <djgpp AT delorie DOT com> |
Subject: | Re: Another aspect of free() ? |
References: | <199701090726 DOT KAA00800 AT marstu DOT mari DOT su> |
Serge Golovin wrote: > > Dim Zegebart wrote: > > If I'm use MALLOC for allocating memory can I > > use XFREE for freeing allocated memory or I have to > > use FREE. > Why do you need XFREE while FREE exists? If argument for FREE eq NULL you get the problem. :-( Instead XFREE correctly process NULL value. The problem is what you need xmalloc (i think so) for allocating memory to be freeing by xfree. Am i right ? -- Regards, Dim Zegebart, Moscow Russia.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |