------- Comment #26 from lopresti at gmail dot com 2007-02-01 02:17 -------
I found this PR because I tried calling what() on a bad_alloc, was surprised by
what I got, and did a search. This is my perspective as a random end user;
make of it what you will.
I think "std::bad_alloc" is an improvement. But I was actually expecting
what() to provide something human readable and very specific, like "out of
memory" or "heap corrupted". In my case, I already know the exception is a
std::bad_alloc; I could generate that particular constant string myself...
I find it remarkable that this PR is almost two years old.
--
lopresti at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lopresti at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14493
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
