14 Sep
2017
14 Sep
'17
10:50 p.m.
On 2017-09-14 15:54, Steve Nickolas wrote:
You got perror(), use it (not you)... >_>
All my code that outputs error messages for stuff in the C library
uses perror(), so a typical error might be "foo: cannot open file bar:
No such file or directory", with the last part coming from the C
runtime itself.
This only works if you call libc directly, or if the code you call
(including your own) reuses libc errno codes. If you deal with libfoo,
libfoo has its own error codes, and has no perror-like function, you
must write your own :(
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
Do obvious transformation on domain to reply privately _only_ on Usenet.