There is a fundamental problem with having an `errno` codeset that contains numeric codes, namely that the numerics are OS-dependent. For example, ENOENT is 1 pretty much everywhere (though on IBM Z/OS it's 3465), but ENAMETOOLONG is 36 on Linux, 63 on BSD and MacOS, 91 on Cygwin, 38 on Windows, etc. etc.
On Thu, Nov 3, 2022 at 6:10 PM Arthur A. Gleckler <[email protected]> wrote: > Scheme Request for Implementation 238, > "Codesets," > by Lassi Kortela, > is now available for discussion. > > Its draft and an archive of the ongoing discussion are available at > https://srfi.schemers.org/srfi-238/. > > You can join the discussion of the draft by filling out the subscription > form on that page. > > You can contribute a message to the discussion by sending it to > [email protected]. > > Here's the abstract: > > Many programming interfaces rely on a set of condition codes where each > code has a numeric ID, a mnemonic symbol, and a human-readable message. > This SRFI defines a facility to translate between numbers and symbols in a > codeset and fetch messages by code. Examples are given using the Unix > *errno* and *signal* codesets. > > Regards, > > > SRFI Editor >
