Sender:	richdawe AT bigfoot DOT com
Message-ID:	<39F8B9D7.8C58CEE9@bigfoot.com>
Date:	Fri, 27 Oct 2000 00:10:15 +0100
From:	Richard Dawe <richdawe AT bigfoot DOT com>
X-Mailer:	Mozilla 4.51 [en] (X11; I; Linux 2.2.17 i586)
X-Accept-Language:	de,fr
MIME-Version:	1.0
To:	DJGPP workers <djgpp-workers AT delorie DOT com>
Subject:	Suggested clarification to realloc() info doc
Reply-To:	djgpp-workers AT delorie DOT com

Hello.

Please find a suggested clarification to the realloc() doc below. This
aspect of "has it been freed or not" gets me everytime I use realloc().

Bye, Rich

*** src/libc/ansi/stdlib/malloc.txh.orig        Thu Oct 26 23:56:08 2000
--- src/libc/ansi/stdlib/malloc.txh     Fri Oct 27 00:04:38 2000
***************
*** 81,91 ****
  allocate a new memory space to satisfy the request.  In either case, it
  will return the pointer that you should use to refer to the (possibly
  new) memory area.  The pointer passed may be @code{NULL}, in which case
! this function acts just like @code{malloc} (@pxref{malloc}).

  @subheading Return Value

! A pointer to the memory you should now refer to.

  @subheading Portability

--- 81,92 ----
  allocate a new memory space to satisfy the request.  In either case, it
  will return the pointer that you should use to refer to the (possibly
  new) memory area.  The pointer passed may be @code{NULL}, in which case
! this function acts just like @code{malloc} (@pxref{malloc}).

  @subheading Return Value

! On success, a pointer is returned to the memory you should now refer to.
! On failure, @code{NULL} is returned and @var{ptr} is not freed.

  @subheading Portability

- Raw text -