[committed] libstdc++: Fix outdated docs about demangling exception messages
Checks
Commit Message
Pushed to trunk.
-- >8 --
The string returned by std::bad_exception::what() hasn't been a mangled
name since PR libstdc++/14493 was fixed for GCC 4.2.0, so remove the
docs showing how to demangle it.
libstdc++-v3/ChangeLog:
* doc/xml/manual/extensions.xml: Remove std::bad_exception from
example program.
* doc/html/manual/ext_demangling.html: Regenerate.
---
libstdc++-v3/doc/html/manual/ext_demangling.html | 13 ++-----------
libstdc++-v3/doc/xml/manual/extensions.xml | 13 ++-----------
2 files changed, 4 insertions(+), 22 deletions(-)
@@ -534,14 +534,6 @@ int main()
int status;
char *realname;
- // exception classes not in <stdexcept>, thrown by the implementation
- // instead of the user
- std::bad_exception e;
- realname = abi::__cxa_demangle(e.what(), 0, 0, &status);
- std::cout << e.what() << "\t=> " << realname << "\t: " << status << '\n';
- free(realname);
-
-
// typeid
bar<empty,17> u;
const std::type_info &ti = typeid(u);
@@ -559,7 +551,6 @@ int main()
<screen>
<computeroutput>
- St13bad_exception => std::bad_exception : 0
3barI5emptyLi17EE => bar<empty, 17> : 0
</computeroutput>
</screen>
@@ -568,8 +559,8 @@ int main()
The demangler interface is described in the source documentation
linked to above. It is actually written in C, so you don't need to
be writing C++ in order to demangle C++. (That also means we have to
- use crummy memory management facilities, so don't forget to free()
- the returned char array.)
+ use crummy memory management facilities, so don't forget to
+ <code>free()</code> the returned char array.)
</para>
</chapter>