Date: Mon, 27 Aug 2001 13:47:52 -0500 From: Alfred Perlstein <bright@mu.org> To: Charles Randall <crandall@matchlogic.com> Cc: "'freebsd-hackers@freebsd.org'" <freebsd-hackers@freebsd.org> Subject: Re: Portability of #warning in /usr/include Message-ID: <20010827134752.G81307@elvis.mu.org> In-Reply-To: <5FE9B713CCCDD311A03400508B8B30130828F33F@bdr-xcln.corp.matchlogic.com>; from crandall@matchlogic.com on Fri, Aug 24, 2001 at 10:29:39AM -0600 References: <5FE9B713CCCDD311A03400508B8B30130828F33F@bdr-xcln.corp.matchlogic.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* 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. -- -Alfred Perlstein [alfred@freebsd.org] Ok, who wrote this damn function called '??'? And why do my programs keep crashing in it? 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?20010827134752.G81307>