From: Jeff Davis <pgsql@j-davis.com>
To: Tatsuo Ishii <ishii@postgresql.org>
Cc: pgsql-hackers@postgresql.org
Subject: Re: C11: should we use char32_t for unicode code points?
Date: Fri, 24 Oct 2025 08:25:27 -0700
Message-ID: <435cf6bcf14bb91235da065c70d782863ca9b80e.camel@j-davis.com> (raw)
In-Reply-To: <20251024.184315.1449345234035166124.ishii@postgresql.org>
References: <bedcc93d06203dfd89815b10f815ca2de8626e85.camel@j-davis.com>
<20251024.184315.1449345234035166124.ishii@postgresql.org>
On Fri, 2025-10-24 at 18:43 +0900, Tatsuo Ishii wrote:
>
> Unless char32_t is solely used for the Unicode code point data, I
> think it would be better to define something like "pg_unicode" and
> use
> it instead of directly using char32_t because it would be cleaner for
> code readers.
That was my original idea, but then I saw that apparently char32_t is
intended for Unicode code points:
https://www.gnu.org/software/gnulib/manual/html_node/The-char32_005ft-type.html
But I am also OK with a new type if others find it more readable.
Regards,
Jeff Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: pgsql@j-davis.com, ishii@postgresql.org
Subject: Re: C11: should we use char32_t for unicode code points?
In-Reply-To: <435cf6bcf14bb91235da065c70d782863ca9b80e.camel@j-davis.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox