From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6123 invoked by alias); 9 Mar 2004 04:45:25 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 6116 invoked by uid 48); 9 Mar 2004 04:45:25 -0000 Date: Tue, 09 Mar 2004 04:45:00 -0000 Message-ID: <20040309044525.6115.qmail@sources.redhat.com> From: "zack at gcc dot gnu dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040308221042.14493.debian-gcc@lists.debian.org> References: <20040308221042.14493.debian-gcc@lists.debian.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug libstdc++/14493] No std::bad_alloc::what() const X-Bugzilla-Reason: CC X-SW-Source: 2004-03/txt/msg01082.txt.bz2 List-Id: ------- Additional Comments From zack at gcc dot gnu dot org 2004-03-09 04:45 ------- It appears to me that the original reporter wanted what() to return an "intelligible error message" a la icc's "bad allocation", rather than "St9bad_alloc" (which does communicate the same information but in a more cryptic fashion). I do think there should be a place in the standard library for nice friendly names for exceptions (think strerror()), but I don't know if what() is that place. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14493