From: Jonny Grant <jg@jguk.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>,
Andrew Pinski <pinskia@gmail.com>
Cc: GCC <gcc@gcc.gnu.org>
Subject: Re: wwwdocs: cxx-reflection/index.html Standardeze
Date: Sun, 3 Dec 2023 11:53:04 +0000 [thread overview]
Message-ID: <49dae060-c19f-46bd-b55f-5003165b9d0f@jguk.org> (raw)
In-Reply-To: <CAH6eHdSavrS8Wi7kscvLz_MH4MKy3zhv8Czt1Wae3Jf7jRBKFQ@mail.gmail.com>
On 03/12/2023 10:11, Jonathan Wakely wrote:
>
>
> On Sun, 3 Dec 2023, 02:18 Andrew Pinski via Gcc, <gcc@gcc.gnu.org <mailto:gcc@gcc.gnu.org>> wrote:
>
> On Sat, Dec 2, 2023 at 5:40 PM Jonny Grant <jg@jguk.org <mailto:jg@jguk.org>> wrote:
> >
> > Hello
> >
> > I held of making a patch to change this (to remove it), does Standardeze mean something:
> >
> > https://gcc.gnu.org/projects/cxx-reflection/index.html <https://gcc.gnu.org/projects/cxx-reflection/index.html>
>
> It means written in the same form as the language that is the C++
> standard. It is a term which is used to describe that the language
> that the C++ standard uses sometimes can be hard to read due to the
> terms used which is not how C++ developers know them as.
>
>
> Literally, the language of the standard. Like legalese:
> https://dictionary.cambridge.org/dictionary/english/legalese <https://dictionary.cambridge.org/dictionary/english/legalese>
I see. Thank you both for clarifying.
Jonny
>
>
>
> The project and C++ has moved on from the time it was being developed
> even. concepts in C++20 seems like the evolution of that work even.
>
>
> Things have moved as far as actual reflection in the language being proposed for C++26:
> https://wg21.link/p2996r0 <https://wg21.link/p2996r0>
>
prev parent reply other threads:[~2023-12-03 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 0:36 Jonny Grant
2023-12-03 2:16 ` Andrew Pinski
2023-12-03 10:11 ` Jonathan Wakely
2023-12-03 11:53 ` Jonny Grant [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=49dae060-c19f-46bd-b55f-5003165b9d0f@jguk.org \
--to=jg@jguk.org \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=pinskia@gmail.com \
/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).