Remove the description of EBADF (that's an implementation detail if I

ever saw one), and move the description of NULL behaviour out to a
'NOTES' section, with an extra note that programs should not rely up
on it.

Kinda-approve-by:	bde (by not replying to the mail with the diff)

1 files changed, 6 insertions, 11 deletions

diff --git a/lib/libc/stdio/fclose.3 b/lib/libc/stdio/fclose.3
index e8c4066..61822e5 100644
--- a/lib/libc/stdio/fclose.3
+++ b/lib/libc/stdio/fclose.3
@@ -1,4 +1,4 @@
->.\" Copyright (c) 1990, 1991, 1993
+.\" Copyright (c) 1990, 1991, 1993
 .\"	The Regents of the University of California.  All rights reserved.
 .\"
 .\" This code is derived from software contributed to Berkeley by
@@ -63,13 +63,6 @@ is returned and the global variable
 .Va errno
 is set to indicate the error.
 In either case no further access to the stream is possible.
-.Sh ERRORS
-.Bl -tag -width [EBADF]
-.It Bq Er EBADF
-The argument
-.Fa stream
-is not an open stream.
-.El
 .Pp
 The
 .Fn fclose
@@ -80,10 +73,12 @@ for any of the errors specified for the routines
 .Xr close 2
 or
 .Xr fflush 3 .
-If passed a NULL argument, 
+.Sh NOTES
 .Fn fclose
-will dump core.  This is intentional, as it makes it easier to make
-sure programs written under FreeBSD are bug free.
+does not handle NULL arguments; they will result in a segment
+violation.  This is intentional - it makes it easier to make sure
+programs written under FreeBSD are bug free.  This behaviour is an
+implementation detail, and programs should not rely upon it.
 .Sh SEE ALSO
 .Xr close 2 ,
 .Xr fflush 3 ,