From: Joseph Myers <joseph@codesourcery.com>
To: Tom Honermann <tom@honermann.net>
Cc: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH 2/3]: C++20 P0482R6 and C2X N2653: Implement mbrtoc8, c8rtomb, char8_t
Date: Mon, 28 Feb 2022 23:01:35 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2202282300230.2276807@digraph.polyomino.org.uk> (raw)
In-Reply-To: <57610f50-dd95-fd32-1102-5f1cda440891@honermann.net>
On Sun, 27 Feb 2022, Tom Honermann via Libc-alpha wrote:
> This patch provides implementations for the mbrtoc8 and c8rtomb functions
> adopted for C++20 via WG21 P0482R6 [1] and for C2X via WG14 N2653 [2]. It also
> provides the char8_t typedef adopted for C2X via WG14 N2653 [2].
>
> The mbrtoc8 and c8rtomb functions are declared in uchar.h in C2X mode or when
> the _GNU_SOURCE macro or C++20 __cpp_char8_t feature test macro is defined.
>
> The char8_t typedef is declared in uchar.h in C2X mode or when the _GNU_SOURCE
> macro is defined and the C++20 __cpp_char8_t feature test macro is not defined
> (if __cpp_char8_t is defined, then char8_t is a builtin type).
You should almost never have "defined __USE_GNU || ..." in header
conditionals, because _GNU_SOURCE implies the other feature test macros.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-02-28 23:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 16:53 Tom Honermann
2022-02-28 23:01 ` Joseph Myers [this message]
2022-03-01 3:40 ` Tom Honermann
2022-05-17 15:57 ` Carlos O'Donell
2022-05-17 18:05 ` Adhemerval Zanella
2022-05-17 18:12 ` Joseph Myers
2022-05-17 18:17 ` Adhemerval Zanella
2022-05-17 21:33 ` Florian Weimer
2022-05-18 15:32 ` Tom Honermann
2022-05-18 16:17 ` Adhemerval Zanella
2022-05-18 17:26 ` Tom Honermann
2022-05-18 17:39 ` Adhemerval Zanella
2022-05-18 17:40 ` Florian Weimer
2022-05-18 17:57 ` Adhemerval Zanella
-- strict thread matches above, loose matches on Subject: below --
2022-01-08 0:39 Tom Honermann
2022-01-11 0:53 ` Joseph Myers
2022-01-11 19:23 ` Tom Honermann
2022-01-20 23:17 ` Tom Honermann
2022-01-21 20:01 ` Adhemerval Zanella
2022-01-22 12:24 ` Tom Honermann
2022-02-16 18:29 ` Joseph Myers
2022-02-16 19:14 ` tom
2021-06-07 2:08 Tom Honermann
2021-06-07 18:53 ` Joseph Myers
2021-06-11 11:25 ` Tom Honermann
2021-06-11 16:28 ` Joseph Myers
2021-06-13 15:35 ` Tom Honermann
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=alpine.DEB.2.22.394.2202282300230.2276807@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=tom@honermann.net \
/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).