include incompatibilities

David Robinow
Fri Jun 30 09:08:00 GMT 2000

--- wrote:
> I had lamented about incompatible changes in include
> files.
 Incompatible with what?
> May I repeat the practical essence of my previous
> mail which is the 
> question: How can these things be detected by
> #ifdef's without 
> referring to actual system specifics as below?
> #include <errno.h>
> #ifdef __CYGWIN__	/* and version > something ... !
> */
> #define sys_nerr _sys_nerr
> #define sys_errlist _sys_errlist
> #endif
> (On "classical" systems, the exported names are
> without underlines - 
> why do these name manglings have to be imposed on
> us?)
 Looking around the office, I find

IRIX 6.5 sys_nerr and sys_errlist are only defined
with use of the Non-ANSI switch.

Solaris 6.5 sys_nerr and sys_errlist are not defined
at all.

If by "classical" you mean "obsolete" you might have a

It really seems to me that it would be less effort to
change your program than to convince the whole world
to go backward 10 years.

Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere!

Want to unsubscribe from this list?
Send a message to

More information about the Cygwin mailing list