public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [PATCH] libstdc++: Clarify manual demangle doc
@ 2023-06-10 22:03 Jonny Grant
  2023-06-14 14:03 ` Jonathan Wakely
  0 siblings, 1 reply; 2+ messages in thread
From: Jonny Grant @ 2023-06-10 22:03 UTC (permalink / raw)
  To: libstdc++, gcc-patches

libstdc++-v3/ChangeLog:

	* doc/xml/manual/extensions.xml: Remove demangle exception description and include.

---
 libstdc++-v3/doc/xml/manual/extensions.xml | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/libstdc++-v3/doc/xml/manual/extensions.xml b/libstdc++-v3/doc/xml/manual/extensions.xml
index daa98f5cba7..d4fe2f509d4 100644
--- a/libstdc++-v3/doc/xml/manual/extensions.xml
+++ b/libstdc++-v3/doc/xml/manual/extensions.xml
@@ -514,12 +514,10 @@ get_temporary_buffer(5, (int*)0);
     you won't notice.)
   </para>
   <para>
-    Probably the only times you'll be interested in demangling at runtime
-    are when you're seeing <code>typeid</code> strings in RTTI, or when
-    you're handling the runtime-support exception classes.  For example:
+    Probably the only time you'll be interested in demangling at runtime
+    is when you're seeing <code>typeid</code> strings in RTTI.  For example:
   </para>
    <programlisting>
-#include &lt;exception&gt;
 #include &lt;iostream&gt;
 #include &lt;cstdlib&gt;
 #include &lt;cxxabi.h&gt;
-- 
2.37.2

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-06-14 14:03 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-06-10 22:03 [PATCH] libstdc++: Clarify manual demangle doc Jonny Grant
2023-06-14 14:03 ` Jonathan Wakely

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).