public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonny Grant <jg@jguk.org>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [PATCH] libstdc++: Clarify manual demangle doc
Date: Sat, 10 Jun 2023 23:03:40 +0100	[thread overview]
Message-ID: <fbdce7ef-037a-e677-f309-5125cf16e503@jguk.org> (raw)

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

             reply	other threads:[~2023-06-10 22:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-10 22:03 Jonny Grant [this message]
2023-06-14 14:03 ` Jonathan Wakely

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fbdce7ef-037a-e677-f309-5125cf16e503@jguk.org \
    --to=jg@jguk.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).