This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
RE: include incompatibilities
- To: "'towo at computer dot org'" <towo at computer dot org>, cygwin at sourceware dot cygnus dot com
- Subject: RE: include incompatibilities
- From: Heribert Dahms <heribert_dahms at icon-gmbh dot de>
- Date: Mon, 3 Jul 2000 21:22:44 +0200
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@icon-gmbh.de)
> -----Original Message-----
> From: towo@computer.org [SMTP:towo@computer.org]
> Sent: Monday, July 03, 2000 15:37
> To: cygwin@sourceware.cygnus.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@sourceware.cygnus.com