From owner-freebsd-current Mon Mar 1 9:20:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 1B83815517 for ; Mon, 1 Mar 1999 09:20:23 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id JAA22745; Mon, 1 Mar 1999 09:20:06 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id JAA49016; Mon, 1 Mar 1999 09:20:06 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 1 Mar 1999 09:20:06 -0800 (PST) Message-Id: <199903011720.JAA49016@vashon.polstra.com> To: obrien@NUXI.com Subject: Re: gcc In-Reply-To: <19990228233542.A4444@relay.nuxi.com> References: <19990228225739.F3380@relay.nuxi.com> <32636.920273557@zippy.cdrom.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990228233542.A4444@relay.nuxi.com>, David O'Brien wrote: > > guess we shoot for libstdc++ as the "minimum requirements" and perhaps > > provide libg++ as well (not necessarily initially) just for the > > Just make libg++ a port. :-) Yes, or abandon it entirely. We surely don't need it in our base system. Even for ports, I'd be surprised to find anything useful that still relied on libg++. Any software that still uses libg++ is almost certainly unmaintained, and uncompilable with modern C++ compilers. (I.e., it does not conform to the C++ standard.) Libg++ is _ancient_. It pre-dated templates even. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message