Justin, > > Comments below: > > > > > Included is a manpage for error(). Please consider including it. > > > > I am considering it. > > > > > .TH ERROR 3 "25 April 2006" GNU > > > .\" Please adjust this date whenever revising the manpage. > > > > No need for that last line. > It was in the Debian manpage template :)
Oh. Kind of redundant really. > > > This variable can be used to defer and > > > unify error handling for a large code block to a single common > > > handler. > > > > I'm not sure what you are meaning with the above. Please explain. > I think I got this idea from the glibc example program. Consider > ferror(), which allows you to do a whole bunch of stuff on a FILE* > without checking individual function calls for error, and then test > whether they all succeeded with ferror(), and handle it at once. > error() can do the same thing, kind of. You still have to do some > kind of conditionals around the function calls, but you can do the > more elaborate error message in one place. I guess you can do this > anyway with a custom any_err=0, but I was trying to preserve the > interesting usage example. It could be omitted. Yes -- I think I will cut it. > > > If \fIerror_print_progname\fP is set nonnull, then it is called > > > instead of prefixing the message with the program name and colon. > > > > > Note that when \fIerror_print_progname\fP is unset, \fIstdout\fP is > > > cleared before printing to \fIstderr\fP. > > > > Where so you glean this piece of information from? > The header file, /usr/include/error.h. Ahh -- I see it now. But the header file comment isn't right: the code always flushes stdout, regardless of the setting of error_print_progname. > Should I send a tweaked manpage? Not at this stage. I'm editing. Cheers, Michael -- Michael Kerrisk maintainer of Linux man pages Sections 2, 3, 4, 5, and 7 Want to help with man page maintenance? Grab the latest tarball at ftp://ftp.win.tue.nl/pub/linux-local/manpages/, read the HOWTOHELP file and grep the source files for 'FIXME'. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
