From owner-freebsd-hackers Mon Aug 27 11:48: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id A3F7037B405 for ; Mon, 27 Aug 2001 11:48:02 -0700 (PDT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 7E0E281D01; Mon, 27 Aug 2001 13:47:52 -0500 (CDT) Date: Mon, 27 Aug 2001 13:47:52 -0500 From: Alfred Perlstein To: Charles Randall Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: Portability of #warning in /usr/include Message-ID: <20010827134752.G81307@elvis.mu.org> References: <5FE9B713CCCDD311A03400508B8B30130828F33F@bdr-xcln.corp.matchlogic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5FE9B713CCCDD311A03400508B8B30130828F33F@bdr-xcln.corp.matchlogic.com>; from crandall@matchlogic.com on Fri, Aug 24, 2001 at 10:29:39AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Charles Randall [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