[src/trunk]: src/lib/libc/stdlib Remove incorrect comment about size; mention...

[christos <christos%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/2fae848290fa
branches:  trunk
changeset: 335999:2fae848290fa
user:      christos <christos%NetBSD.org@localhost>
date:      Thu Feb 05 22:05:33 2015 +0000

description:
Remove incorrect comment about size; mention that the malloc ambiguity is
part of the C standard.

diffstat:

 lib/libc/stdlib/reallocarray.3 |  15 ++++-----------
 1 files changed, 4 insertions(+), 11 deletions(-)

diffs (38 lines):

diff -r 1942ad90b265 -r 2fae848290fa lib/libc/stdlib/reallocarray.3
--- a/lib/libc/stdlib/reallocarray.3    Thu Feb 05 22:04:03 2015 +0000
+++ b/lib/libc/stdlib/reallocarray.3    Thu Feb 05 22:05:33 2015 +0000
@@ -1,4 +1,4 @@
-.\" $NetBSD: reallocarray.3,v 1.1 2015/02/05 20:02:28 christos Exp $
+.\" $NetBSD: reallocarray.3,v 1.2 2015/02/05 22:05:33 christos Exp $
 .\"
 .Dd February 5, 2015
 .Dt REALLOCARRAY 3
@@ -84,17 +84,10 @@
 and
 .Fa size .
 .Pp
-Implementation issues prevent the function from being used correctly (a
-.Dv 0
-.Fa size
-parameter will return
-.Dv ENOMEM
-in the
-.Ox
-implementation), while there are still portability issues (it does not solve
+There are still portability issues (it does not solve
 the 
 .Dv 0
-sized allocation return ambiguity: does
+sized allocation return ambiguity in the C standard: does
 .Fn reallocarray
 return
 .Dv NULL
@@ -104,7 +97,7 @@
 .Dv errno
 in that case to find out what happened?).
 .Pp
-For those reasons
+For this reason
 .Nx
 decided to go with an alternative implementation, and created
 .Xr reallocarr 3 .