`errno` is a userland concept; the kernel returns negative error numbers that libc then turns into -1 and sets errno. Thus the correct manpage is errno(3).
replyOpenBSD up to 5.9 had errno(2) symlinked to intro(2), describing error codes:
replyhttps://man.freebsd.org/cgi/man.cgi?query=errno&apropos=0&se...
Also, your statements about the kernel and libc are OS specific.
Why does libc do this instead of simply returning that same negative number?
replyPOSIX, basically. It was already a convention by the time linux/glibc implemented it.
replydeleted
reply #define ETERNITY 999 /* stuck in thinking loop */Missed one...
reply EHAL 231 /* I'm sorry Dave, I cannot do that */As a long time emacs user, I appreciated the inclusion of EMACS as an error code. When I moved from TECO to gnu emacs in to 80s, elisp was an advance. Now I have a perpetual todo item... "rewrite emacs in fennel or janet or even minimalisp."
reply"What was deluxe is now debris..."
> #define EAI 201 /* hallucination */
replyIf only AI threw an error when it hallucinates.
Nah it would just hallucinate this error all the time
replyIt would hallucinate error codes that don't exist.
reply #define EPROCRASTINATE 245 /* exhausted all output tokens with reasoning */#define EKNOWBETTER 231 # ignoring prompt
reply#define ESYCOPHANT 200 /* user asserted 2+2=5; model concurred */
replyI often ran into an error where multimodal models would refuse to operate in transcription mode due to some system prompt.
reply207 is a bald move
replywhat about ETHOS : Error it's Mythos? lol!
replyETHOS is generally reserved for a certain type of error involving slab memory and complex logic though.
replyLet's hope that reference is not too obscure...