Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <20000630160833.712.qmail@web2106.mail.yahoo.com> Date: Fri, 30 Jun 2000 09:08:33 -0700 (PDT) From: David Robinow Subject: Re: include incompatibilities To: towo AT computer DOT org, cygwin AT sourceware DOT cygnus DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- towo AT computer DOT org 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 > #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 point. 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! http://mail.yahoo.com/ -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com