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: "gdr at integrable-solutions dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 11 Mar 2004 10:05:49 -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 gdr at integrable-solutions dot net 2004-03-11 10:05 -------
Subject: Re: No std::bad_alloc::what() const
"pme at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes:
| > Especially compared to "bad allocation"?
|
| Sure, we could change that. I don't think "bad allocation" is any
| better than the demangled type name, but we shouldn't be printing
| a mangled typeid. Others felt differently.
I agree with Phil that we should not have been printing the mangled
typeid.
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14493