From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [committed] doc: Update references to "C++2a" in cpp.texi
Date: Fri, 4 Feb 2022 15:27:43 +0000 [thread overview]
Message-ID: <20220204152743.2632220-1-jwakely@redhat.com> (raw)
Committed as obvious.
gcc/ChangeLog:
* doc/cpp.texi (Variadic Macros): Replace C++2a with C++20.
---
gcc/doc/cpp.texi | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/gcc/doc/cpp.texi b/gcc/doc/cpp.texi
index d4290fefb41..90b2767e39a 100644
--- a/gcc/doc/cpp.texi
+++ b/gcc/doc/cpp.texi
@@ -1678,7 +1678,7 @@ This formulation looks more descriptive, but historically it was less
flexible: you had to supply at least one argument after the format
string. In standard C, you could not omit the comma separating the
named argument from the variable arguments. (Note that this
-restriction has been lifted in C++2a, and never existed in GNU C; see
+restriction has been lifted in C++20, and never existed in GNU C; see
below.)
Furthermore, if you left the variable argument empty, you would have
@@ -1690,10 +1690,10 @@ eprintf("success!\n", );
@expansion{} fprintf(stderr, "success!\n", );
@end smallexample
-This has been fixed in C++2a, and GNU CPP also has a pair of
+This has been fixed in C++20, and GNU CPP also has a pair of
extensions which deal with this problem.
-First, in GNU CPP, and in C++ beginning in C++2a, you are allowed to
+First, in GNU CPP, and in C++ beginning in C++20, you are allowed to
leave the variable argument out entirely:
@smallexample
@@ -1702,7 +1702,7 @@ eprintf ("success!\n")
@end smallexample
@noindent
-Second, C++2a introduces the @code{@w{__VA_OPT__}} function macro.
+Second, C++20 introduces the @code{@w{__VA_OPT__}} function macro.
This macro may only appear in the definition of a variadic macro. If
the variable argument has any tokens, then a @code{@w{__VA_OPT__}}
invocation expands to its argument; but if the variable argument does
--
2.34.1
reply other threads:[~2022-02-04 15:27 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=20220204152743.2632220-1-jwakely@redhat.com \
--to=jwakely@redhat.com \
--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).