From owner-freebsd-current Mon Mar 9 15:58:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06159 for freebsd-current-outgoing; Mon, 9 Mar 1998 15:58:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05805 for ; Mon, 9 Mar 1998 15:57:27 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id SAA25936; Mon, 9 Mar 1998 18:55:22 -0500 (EST) Date: Mon, 9 Mar 1998 18:55:21 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: Brian Feldman cc: freebsd-current@FreeBSD.ORG Subject: Re: C++ libs are broken In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Mar 1998, Brian Feldman wrote: > > You know, I'm surprised I've only seen this twice (cut out the damn > stackable FS talk, so we can talk about what's happening NOW!), and have > noticed it quite a bit myself, that the newest C++ libraries ARE BROKEN! I > wish someone might pay a tiny bit of attention to this, because it's > really annoying (2.2.5-RELEASE's C++ libs are less than fully functional > to use). Might someone want to see what commit changes have been made and > fix these libraries? Keep some perspective ... current's been the target of some folks who abused the privilege, but the stuff about the filesystems IS a good, and really interesting "current" topic. You can ask about the C++ libs, but not at the expense of what others are doing ... that's selfish. Besides, if you're reading the commit mail, you know that the C++ libs are currently the topic of a lot of work, they haven't been badly busted all that long, give them some time. They already know things are unstable (the reason is because the ELF stuff *and* the Alpha stuff are both hitting the C++ libs at the same time) so this just calls for a little patience. A heads up ("this is broken") is a good thing, but not calling off debate of important topics in design. > > -Brian Feldman > brianfeldman@hotmail.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message