[src/trunk]: src/lib/libc/string Mention err/warn. Note that they're generall...

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

details:   https://anonhg.NetBSD.org/src/rev/0d0bd8120c09
branches:  trunk
changeset: 758185:0d0bd8120c09
user:      dholland <dholland%NetBSD.org@localhost>
date:      Sun Oct 24 23:10:51 2010 +0000

description:
Mention err/warn. Note that they're generally preferred to perror().
Might want to strengthen the wording.

diffstat:

 lib/libc/string/strerror.3 |  13 +++++++++++--
 1 files changed, 11 insertions(+), 2 deletions(-)

diffs (34 lines):

diff -r 326cbd718e20 -r 0d0bd8120c09 lib/libc/string/strerror.3
--- a/lib/libc/string/strerror.3        Sun Oct 24 22:37:35 2010 +0000
+++ b/lib/libc/string/strerror.3        Sun Oct 24 23:10:51 2010 +0000
@@ -1,4 +1,4 @@
-.\" $NetBSD: strerror.3,v 1.15 2006/10/16 08:48:45 wiz Exp $
+.\" $NetBSD: strerror.3,v 1.16 2010/10/24 23:10:51 dholland Exp $
 .\"
 .\" Copyright (c) 1980, 1991, 1993
 .\"    The Regents of the University of California.  All rights reserved.
@@ -98,6 +98,13 @@
 a colon and space
 .Pq Dq Li ":\ " ;
 otherwise, only the error message string is printed.
+Note that in most cases the
+.Xr err 3
+and
+.Xr warn 3
+family of functions is preferable to
+.Fn perror ;
+they are more flexible and also print the program name.
 .Pp
 If the error number is not recognized, these functions pass an error message
 string containing
@@ -148,7 +155,9 @@
 should be used instead.
 .Sh SEE ALSO
 .Xr intro 2 ,
-.Xr psignal 3
+.Xr err 3 ,
+.Xr psignal 3 ,
+.Xr warn 3
 .Sh STANDARDS
 The
 .Fn perror