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

[Bug libstdc++/14493] No std::bad_alloc::what() const



------- Additional Comments From zack at codesourcery dot com  2004-03-09 20:14 -------
Subject: Re:  No std::bad_alloc::what() const

"pme at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes:
>> 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).
>
> Slap a _Z on that thing and we could demangle it automatically.  The
> problems with doing so are that the demangling routines are linked in
> when they otherwise wouldn't be (so goes the argument, but I haven't
> verified it myself).

Honestly, is "std::bad_alloc" really that much more readable than
"St9bad_alloc"?  Especially compared to "bad allocation"?

zw


-- 


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.



Reply to: