svn commit: r252672 - head/sbin/nvmecontrol
brde at optusnet.com.au
Sun Jul 7 08:30:19 UTC 2013
> One minor interjection and I'll butt out of the discussion...
>> In another thread involving Pawel, phk campaigns against errno and asks
>> for error strings (even if they are only in English). Using perror()
>> did this long ago for program termination, and using the err() family
>> does it better. Except possibly for program suites -- translating a
>> single numeric error is easier for programs than translating an
>> unstructured string. I actually prefer using binary representations
>> for programs.
> Your argument would be valid if computers were parsing output and putting it in more meaningful forms, but it's invalid when humans need to understand why things fail. Many devs who consume FreeBSD don't understand the concept of man 5 errno, and if they don't, I doubt end-users of FreeBSD (and its derivatives) will.
That was more than half of my argument. perror() and err() give messages
that are readable by humans. Extra info in exit statuses adds less than
nothing for most humans. Some programs can parse it, but most can't.
Sysexits is thus useless for almost everything.
More information about the svn-src-head