[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#236912: [Bug libstdc++/14493] 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




Reply to: