groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [groff] Asynchronous events


From: James K. Lowden
Subject: Re: [groff] Asynchronous events
Date: Wed, 12 Dec 2018 09:40:39 -0500

On Wed, 12 Dec 2018 03:32:11 +0100
Ingo Schwarze <address@hidden> wrote:

>  * ERRORS.
>    Most system call pages and many library function pages have
>    this section, but the information being complete is the
>    exception rather than the norm.  Even in OpenBSD.

That's especially true for network functions.  And unnecessary: static
analysis could report every function call and every value of errno
set by each function.  That database could be compared to the
enumerated set in the documentation; the man pages could even be
automatically updated to reflect the potential (undocumented)
diagnostics and their origins.  Then guys like Branden could swoop in
and fix the semi-corrected documentation.  

A similar scan for diagnostics could be made for calls to err(3) and
friends.  Yes, errors are emitted other ways, but if the scan was
conducted periodically, it would encourage use of the those functions. 

Only a matter of time. 

--jkl




reply via email to

[Prev in Thread] Current Thread [Next in Thread]