From owner-freebsd-current Thu May 28 13:15:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15332 for freebsd-current-outgoing; Thu, 28 May 1998 13:15:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15240 for ; Thu, 28 May 1998 13:15:04 -0700 (PDT) (envelope-from piquan@wcc.net) Received: from detlev.UUCP (tex-135.camalott.com [208.229.74.135] (may be forged)) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id PAA04296; Thu, 28 May 1998 15:08:40 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id PAA01643; Thu, 28 May 1998 15:09:40 -0500 (CDT) (envelope-from joelh) Date: Thu, 28 May 1998 15:09:40 -0500 (CDT) Message-Id: <199805282009.PAA01643@detlev.UUCP> To: rnordier@nordier.com CC: eivind@yes.no, current@FreeBSD.ORG In-reply-to: <199805281905.VAA26880@ceia.nordier.com> (message from Robert Nordier on Thu, 28 May 1998 21:05:42 +0200 (SAT)) Subject: Re: Fix for undefined "__error" and discussion of shared object versioning From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199805281905.VAA26880@ceia.nordier.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> The critical issue, however, is really whether it is feasible to >>> compile *FreeBSD* with a non-GCC compiler. Any real problems will >>> be due to FreeBSD (GCC quirks in the code) not to the compiler. >>> (There are no fundamental difficulties inherent in compiling >>> UNIX-like systems). >> My own concern would be the amount of code in third-party programs >> that uses gccisms. I guess I don't see why we're looking to change. > A reasonable point. TenDRA does have a more relaxed mode, but > there are various things it can't handle. For instance, using cast > expressions as lvalues (perhaps that's a pc-ism). No, you're right, casts as lvalues is a gccism (along with ?: and , in lvalues). My main concerns are inline, long long, typeof, nested functions, and extensions to asm. Now, I'll grant you that the last three we most frequently get in through software from the GNU/Linux camps, but I still like the software and want to be able to use it. A question: Who knows how we are on gccisms in our assembly routines? > I only want to be *able* to change: > If you love gcc, let it go. > If it stays, it is suitable > If not, it never was. > 8-) Cute. :-) Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message