From owner-freebsd-current Mon Sep 2 10:19:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 148BA37B4B1 for ; Mon, 2 Sep 2002 10:19:07 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DD9743E4A for ; Mon, 2 Sep 2002 10:19:06 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.5/8.12.2) with ESMTP id g82HJ5im003642; Mon, 2 Sep 2002 10:19:05 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.5/8.12.5/Submit) id g82HJ3w9003505; Mon, 2 Sep 2002 10:19:03 -0700 (PDT) Date: Mon, 2 Sep 2002 10:19:03 -0700 From: "David O'Brien" To: Lamont Granquist Cc: freebsd-current@FreeBSD.ORG Subject: Re: gcc 3.1 / streambuf.h broken with "using namespace std;" Message-ID: <20020902171903.GA5232@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20020901230840.GA37166@dragon.nuxi.com> <20020902021408.R14754-100000@coredump.scriptkiddie.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020902021408.R14754-100000@coredump.scriptkiddie.org> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 02, 2002 at 02:17:25AM -0700, Lamont Granquist wrote: > On Sun, 1 Sep 2002, David O'Brien wrote: > > On Sun, Sep 01, 2002 at 12:37:14PM -0700, Lamont Granquist wrote: > > > It sounds like gcc-3.1 or gcc-3.2 will be archaic and buggy > > > by the time that 5.2 and 5.3 come out. > > > > How would gcc-3.2 get more buggy over time than it is today?? > > I said it was buggy. Do you mean to imply that gcc-3.2 doesn't have a > single bug in it? Labling software as "buggy" is a major put down. If GCC 3.2 is "buggy" because it has at least one bug; then FreeBSD 4.7 will also be buggy as hell. > Admittedly I should have said "unmaintained" though -- point being that > the bugs in it wouldn't be getting fixed by gcc developers who would > rather fix them in 3.3... We don't maintain 3.x either -- much to the disappointment of some that based products or major deployments on it. But I do think we support the current release branch much better than the GCC people do. We have a much more liberal MFC policy which lets us continue to fix invasive bugs and add new features. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message