This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/14493] No std::bad_alloc::what() const
- From: "jtv at xs4all dot nl" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 9 Mar 2004 18:32:43 -0000
- Subject: [Bug libstdc++/14493] No std::bad_alloc::what() const
- References: <20040308221042.14493.debian-gcc@lists.debian.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From jtv at xs4all dot nl 2004-03-09 18:32 -------
Subject: Re: No std::bad_alloc::what() const
On Tue, Mar 09, 2004 at 06:14:59AM +0100, Matthias Klose wrote:
> > More to the point, it doesn't matter how it's implemented, and the user
> > should not care. It only matters that
> >
> > std::bad_alloc foo;
> > std::cerr << foo.what() << std::endl;
> >
> > works, which the submitter didn't apparently try. Looking at the original
Apparently whoever said this hasn't seen the bug report, and it got
rephrased somewhere along the line. I was wrong in my assumption that
std::bad_alloc should override what(), but the problem remains: the
message coming out of what(), "St9bad_alloc" is incomprehensible to
a normal user.
Jeroen
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14493