From: Mark Wooding <mdw@distorted.org.uk>
Date: Sun, 13 May 2018 11:30:06 +0000 (+0100)
Subject: server/admin.c (a_format): Introduce `?ERR' for explicitly named errors.
X-Git-Tag: 1.5.0~28
X-Git-Url: https://git.distorted.org.uk/~mdw/tripe/commitdiff_plain/e4b47618f00dc9ae93ccc24a9271d92faec63536?hp=e4b47618f00dc9ae93ccc24a9271d92faec63536

server/admin.c (a_format): Introduce `?ERR' for explicitly named errors.

Judging by the documentation, `?ERRNO' is supposed to take an `int'
argument and format the error it specifies; but it actually works by
examining `errno', and all the callers know this.  Changing it now seems
pointless, but I do want to be able to report errors in cases where
`errno' is or might be stale, and stuffing an error code back into
`errno' just so that it can be reported seems rather ugly.

Instead, add `?ERR' which /does/ accept an `int' argument, and fix the
documentation so that it describes reality.
---