Group Email Manager

login signup
The errno and signal codesets Lassi Kortela (13 Dec 2022 11:38 UTC)
Re: The errno and signal codesets Lassi Kortela (13 Dec 2022 11:48 UTC)
Re: The errno and signal codesets John Cowan (14 Dec 2022 05:58 UTC)
Re: The errno and signal codesets Lassi Kortela (14 Dec 2022 09:08 UTC)
Re: The errno and signal codesets John Cowan (14 Dec 2022 22:48 UTC)
Re: The errno and signal codesets Lassi Kortela (15 Dec 2022 09:10 UTC)
Re: The errno and signal codesets John Cowan (18 Dec 2022 07:56 UTC)
Re: The errno and signal codesets Lassi Kortela (20 Dec 2022 10:51 UTC)
Re: The errno and signal codesets Lassi Kortela (20 Dec 2022 11:53 UTC)
Re: The errno and signal codesets Lassi Kortela 14 Dec 2022 09:08 UTC 
> Given a number, as by checking errno or the first argument of a signal
> handler, it makes sense to be able to return a symbol, but there is no
> need to convert the symbol to a number whose value is machine- and
> OS-dependent.  I think for that reason `codeset-number` should be
> removed from the SRFI.

It's handy for introspection purposes (REPL use, logs, etc.)

C and Python programmers can easily find the integer corresponding to a
given errno symbol on the local machine. Have they been abusing this
capability?