From: Michael Kerrisk <mtk.manpages@gmail.com>
Date: Fri, 22 Feb 2008 10:06:08 +0000 (+0000)
Subject: Clarify description of realloc() behavior for ((size == 0) && (ptr != NULL)).
X-Git-Tag: man-pages-2.79~42
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=c4acc6895ae3ea0b4136661776c6e370641ad34c;p=thirdparty%2Fman-pages.git

Clarify description of realloc() behavior for ((size == 0) && (ptr != NULL)).
---

diff --git a/man3/malloc.3 b/man3/malloc.3
index 8f7436422e..deba0ecc8f 100644
--- a/man3/malloc.3
+++ b/man3/malloc.3
@@ -25,7 +25,7 @@
 .\" Documented MALLOC_CHECK_, Wolfram Gloger (wmglo@dent.med.uni-muenchen.de)
 .\" 2007-09-15 mtk: added notes on malloc()'s use of sbrk() and mmap().
 .\"
-.TH MALLOC 3  2007-09-15 "GNU" "Linux Programmer's Manual"
+.TH MALLOC 3  2008-02-22 "GNU" "Linux Programmer's Manual"
 .SH NAME
 calloc, malloc, free, realloc \- Allocate and free dynamic memory
 .SH SYNOPSIS
@@ -98,12 +98,14 @@ The contents will be unchanged to the minimum of the old and new sizes;
 newly allocated memory will be uninitialized.
 If
 .I ptr
-is NULL, the call is equivalent to
+is NULL, then the call is equivalent to
 .IR malloc(size) ;
 if
 .I size
 is equal to zero,
-the call is equivalent to
+and
+.I ptr
+is not NULL, then the call is equivalent to
 .IR free(ptr) .
 Unless
 .I ptr