From owner-freebsd-chat Thu May 28 16:08:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19686 for freebsd-chat-outgoing; Thu, 28 May 1998 16:08:46 -0700 (PDT) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19644 for ; Thu, 28 May 1998 16:08:27 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id RAA13102; Thu, 28 May 1998 17:08:20 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id RAA21910; Thu, 28 May 1998 17:08:14 -0600 Date: Thu, 28 May 1998 17:08:14 -0600 Message-Id: <199805282308.RAA21910@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: alk@pobox.com Cc: chat@FreeBSD.ORG, nate@mt.sri.com Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <199805282249.RAA03682@pobox.com> References: <199805282249.RAA03682@pobox.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > My own concern would be the amount of code in third-party programs > > > that uses gccisms. > > > > Very few programs *should* use gccisms. If they do, they are broke > > since they won't build on other OS's compilers. > > [ note redirect to chat ] > > Various points: > > 1 Non-portable != broken. True. *I* consider non-portable code broken. :) > 2 I'm amazed to see this coming from Nate "Java" Williams! That's why I said it. :) > Gcc is the *platform*. Gcc is what makes code portable, > not ANSI, which is merely an idea, and not a platform. *laugh* Note quite. > 3 People use gccisms because then they don't have to write asm, > which is much *less* portable. No, people use gccisms because it's easy. Very few Linux programs that are Linux-centric involve inline asm. There are other gccisms that have been encouraged as 'the right way to do things' simply because it locks you into using GCC IMHO. > 4 Are you planning on fixing them? Egad, the number of ports! Which ports *require* GCC? This is something I'd like to know. > > Better/faster/less buggy compiler with a much less restrictive Copyright > > seems like a win overall to me. > > Remains to be seen, as far as I am concerned. Various points: > > 1 TenDRA should be compared to GCC 2.8.1, not 2.7.2.1. > > 2 GPL should not be a restriction... But it is. People who use FreeBSD in 'embedded' markets may want to keep the compiler, but don't really want to pay the penalty of distributing to anyone that asks, or give them a way to access the source easily. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message