public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r14-1809] libstdc++: Clarify manual demangle doc Date: Wed, 14 Jun 2023 14:02:19 +0000 (GMT) [thread overview] Message-ID: <20230614140219.A50ED3858D38@sourceware.org> (raw) https://gcc.gnu.org/g:29aef9ff236022ebf566738f9bd08bb5e28fe6ca commit r14-1809-g29aef9ff236022ebf566738f9bd08bb5e28fe6ca Author: Jonny Grant <jg@jguk.org> Date: Sat Jun 10 23:03:40 2023 +0100 libstdc++: Clarify manual demangle doc libstdc++-v3/ChangeLog: * doc/xml/manual/extensions.xml: Remove demangle exception description and include. * doc/html/manual/ext_demangling.html: Regenerate. Diff: --- libstdc++-v3/doc/html/manual/ext_demangling.html | 6 ++---- libstdc++-v3/doc/xml/manual/extensions.xml | 6 ++---- 2 files changed, 4 insertions(+), 8 deletions(-) diff --git a/libstdc++-v3/doc/html/manual/ext_demangling.html b/libstdc++-v3/doc/html/manual/ext_demangling.html index 1e7cdda8326..b5fb87b91c5 100644 --- a/libstdc++-v3/doc/html/manual/ext_demangling.html +++ b/libstdc++-v3/doc/html/manual/ext_demangling.html @@ -20,11 +20,9 @@ whole point of abstract interfaces. If we change the implementation, you won't notice.) </p><p> - Probably the only times you'll be interested in demangling at runtime - are when you're seeing <code class="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 class="code">typeid</code> strings in RTTI. For example: </p><pre class="programlisting"> -#include <exception> #include <iostream> #include <cstdlib> #include <cxxabi.h> 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 <exception> #include <iostream> #include <cstdlib> #include <cxxabi.h>
reply other threads:[~2023-06-14 14:02 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230614140219.A50ED3858D38@sourceware.org \ --to=redi@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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: linkBe 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).