Date: Mon, 27 Aug 2001 15:48:07 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: Alfred Perlstein <bright@mu.org>, Charles Randall <crandall@matchlogic.com> Cc: <freebsd-hackers@FreeBSD.ORG> Subject: Re: Portability of #warning in /usr/include Message-ID: <p05101003b7b0537e8277@[128.113.24.47]> In-Reply-To: <20010827134752.G81307@elvis.mu.org> References: <5FE9B713CCCDD311A03400508B8B30130828F33F@bdr-xcln.corp.matchlogic.com> <20010827134752.G81307@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 1:47 PM -0500 8/27/01, Alfred Perlstein wrote: >* Charles Randall <crandall@matchlogic.com> [010827 12:44] wrote: >> I've noted that several include files in /usr/include use the C preprocessor >> #warning directive. This isn't standard C and prevents some software from >> compiling using a compiler like TenDRA. What's the current opinion on this? > >My opinion is that #warning should be standardized, however since it's >not, diffs to surround them with #ifdef __GNU_C__ (or whatever it is) >will probably be committed. This may not work. I know I had some problem with #warn and #warning with some code I was working on, where some C compilers would only recognize one and other C compilers would only recognize the other. Some of those compilers would NOT let you '#ifdef' out the version that it did not recognize (perhaps thinking that '#warn' or '#warning' might be some gross typo for '#else' or '#endif', I guess...). -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05101003b7b0537e8277>