On Thu, 20 Jul 2000, Greg A. Woods wrote:

# It is indeed damn near impossible to always work out exactly what errno
# values the kernel can potentially return from any given system call (or
# indeed a libc function), even by examination of the source as you say
# above.  I firmly believe it is critical that all API manual pages
# document at least the list of error codes that the developers believe
# are possible.  It's not necessary to fully describe what each code means
# when the meaning is indeed identical to the generic description given in
# intro(2) (or intro(3)), and indeed such descriptions should probably not
# be given in order to avoid the maintenance headache of duplicating and
# changing this description.  Certainly I agree that any unique meaning
# must be documented explicitly in the associated manual page.

What's wrong with using the .so directive, and perhaps splitting out
the definitions into smaller files?  It would solve the problem of duplicity.

# I for one will continue to submit fixes for manual pages that do not at
# least list all error codes thought possible....


				--*greywolf;
--
BSD: Microsoft ask you where you want to go.  BSD gets you there.