Date: Wed, 24 Jan 2001 10:05:15 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Jack Klein <jackklein AT spamcop DOT net>
cc: djgpp AT delorie DOT com
Subject: Re: Advance warning of failure of realloc()
In-Reply-To: <SSJtOtOI87FVAoOquAyt63i60RoG@4ax.com>
Message-ID: <Pine.SUN.3.91.1010124100451.25819A@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 23 Jan 2001, Jack Klein wrote:

> I don't have source to DJGPP realloc() handy at the moment, but I
> would be surprised if it did not follow the standard.

DJGPP's implementation supports this feature, but please note that it
comes for a price: if you are enlarging the buffer `realloc' allocates
a new buffer before it frees the old one.  So it can report a failure
even though the remaining amount of memory is large enough to hold the
enlarged buffer.