Mail Archives: cygwin/2000/07/03/15:26:07
Hi Thomas,
why bother about setlocale since strerror should give something anyway?
Then I do not tend to produce unknown errors 8-), but to be sure it's
easy
to print errno also as a number! Including errno.h and using errno and
strerror worked for me on every real Unix variant I had to deal with,
also under NT with Cygwin (of course), but Interix and UWIN as well.
Bye, Heribert (heribert_dahms AT icon-gmbh DOT de)
> -----Original Message-----
> From: towo AT computer DOT org [SMTP:towo AT computer DOT org]
> Sent: Monday, July 03, 2000 15:37
> To: cygwin AT sourceware DOT cygnus DOT com
> Subject: RE: include incompatibilities
>
> [Heribert] [snip]
>
> Also, there are some reasons I did not use strerror().
> One is, strerror may depend on setlocale but setlocale is not
> available
> on older systems. Another is incompatibilities with respect to
> undefined
> values:
> Linux:
> > SYNOPSIS
> > char *strerror(int errnum);
> > RETURN VALUE
> > The strerror() function returns ... an unknown error
> message
> > if the error code is unknown.
>
> Sun:
> > SYNOPSIS
> > char *strerror(int errnum);
> > ERRORS
> > strerror returns NULL if errnum is out-of-range.
>
> So there is no real standard here either...
>
> [Heribert] [snip]
>
> Thomas Wolff
>
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -