From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17608 invoked by alias); 17 Dec 2007 04:34:53 -0000 Received: (qmail 17563 invoked by alias); 17 Dec 2007 04:34:38 -0000 Date: Mon, 17 Dec 2007 04:34:00 -0000 Message-ID: <20071217043438.17562.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/33831] [4.3 Regression] Revision 129442 breaks libstc++ API In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "mark at codesourcery dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-12/txt/msg01575.txt.bz2 ------- Comment #15 from mark at codesourcery dot com 2007-12-17 04:34 ------- Subject: Re: [4.3 Regression] Revision 129442 breaks libstc++ API rguenther at suse dot de wrote: > Now that we have ext/hash_map and ext/hash_set back (yes, SPEC2000 > eon still is broken, as it uses the removed iostream.h and other *.h > headers - and it's impossible to fix without touching all of it) > the issue isn't as pressing anymore. Though still the question > remains if we should break the libstdc++ API at all. There seemed to be pretty good consensus that we shouldn't. So far, other than maintenance pain, I've not seen an argument for removing things like iostream.h. And, I think user pain should trump maintenance pain in this case. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33831