From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Jonny Grant <jg@jguk.org>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Clarify manual demangle doc
Date: Wed, 14 Jun 2023 15:03:01 +0100 [thread overview]
Message-ID: <CAH6eHdQocg03j+MKmdsKCU0t=WovPBnHVm_5otjrwqa_xy2LTQ@mail.gmail.com> (raw)
In-Reply-To: <fbdce7ef-037a-e677-f309-5125cf16e503@jguk.org>
On Sat, 10 Jun 2023 at 23:04, Jonny Grant wrote:
>
> libstdc++-v3/ChangeLog:
>
> * doc/xml/manual/extensions.xml: Remove demangle exception description and include.
Thanks, pushed to trunk.
>
> ---
> 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 <exception>
> #include <iostream>
> #include <cstdlib>
> #include <cxxabi.h>
> --
> 2.37.2
prev parent reply other threads:[~2023-06-14 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-10 22:03 Jonny Grant
2023-06-14 14:03 ` Jonathan Wakely [this message]
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='CAH6eHdQocg03j+MKmdsKCU0t=WovPBnHVm_5otjrwqa_xy2LTQ@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jg@jguk.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).