From ea26437be087a9a07c2505015c0c4a7531e578f5 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Sat, 24 Dec 2022 00:10:23 -0800 Subject: =?UTF-8?q?doc:=20C2x=20=E2=86=92=20C23?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- doc/attribute.texi | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/attribute.texi') diff --git a/doc/attribute.texi b/doc/attribute.texi index f4e18b5169..67fe1f1b7f 100644 --- a/doc/attribute.texi +++ b/doc/attribute.texi @@ -30,7 +30,7 @@ extern char *crypt (char const *, char const *) @noindent @code{NODISCARD} expands to @code{[[nodiscard]]} if the compiler -supports this C2x syntax, otherwise to +supports this C23 syntax, otherwise to @code{__attribute__ ((__warn_unused_result__))} if the compiler is a recent-enough GCC or GCC-like compiler, otherwise to nothing. @code{ATTRIBUTE_NOTHROW} expands to @code{__attribute__ @@ -41,11 +41,11 @@ compiler, and to nothing otherwise. Similarly for recent-enough GCC, and to nothing otherwise. Most of these attribute names begin with @code{ATTRIBUTE_}. -A few do not, because they are part of C2x and their +A few do not, because they are part of C23 and their names are not likely to clash with other macro names. These macros are @code{DEPRECATED}, @code{FALLTHROUGH}, @code{MAYBE_UNUSED}, and @code{NODISCARD}, which can -be defined to @code{[[deprecated]]} etc.@: on C2x platforms. +be defined to @code{[[deprecated]]} etc.@: on C23 platforms. Also, these exceptional macros should be placed at the start of function declarations, whereas the @code{ATTRIBUTE_*} macros can be placed at the end. -- cgit v1.2.1