| |||||||||||||
Making EPERM (un)friendlierMaking EPERM (un)friendlierPosted Jan 20, 2013 8:29 UTC (Sun) by akeane (subscriber, #85436)Parent article: Making EPERM friendlier
POSIX returns too much information as it is, EPERM, ENONENT, ETHIS, ETHAT; it's too confusing!
The only jmp codes that should be popped off the stack should be EFAIL and SSUCCESS, computers are binary after all, if my processor doesn't need more than two states to let me play Doom, then I fail to see why the arrogant C library and POSIX standard should need more. It's complexity for it's own sake...
Maybe as a compromise, some kind soul should hack the C library so it associates an "E" number with a NULL terminated series of bytes which can then be written to a terminal or dot matrix printer.
(Log in to post comments)
Making EPERM (un)friendlier Posted Jan 25, 2013 19:36 UTC (Fri) by nix (subscriber, #2304) [Link]
Sounds like you want the Hurd, with its -EIEIO and -EGREGIOUS errnos. :)
|
|||||||||||||