Re: C11: should we use char32_t for unicode code points? - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: C11: should we use char32_t for unicode code points?
Date
Msg-id 1f4f9efd4e89b2620685b9a6406d832fa16321f2.camel@j-davis.com
Whole thread Raw
In response to Re: C11: should we use char32_t for unicode code points?  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-hackers
On Tue, 2025-10-28 at 19:45 +0100, Peter Eisentraut wrote:
> This could be improved a bit. The reason for some of these
> conditionals
> is not clear.  Like, what does __cplusplus have to do with this?  I
> think it would be more correct to write a configure/meson check for
> the
> actual types rather than depend indirectly on a header check.

Fixed, thank you.

> The checks for __STDC_UTF_16__ and __STDC_UTF_32__ can be removed, as
> was discussed elsewhere, since we don't use any standard library
> functions that make use of these facts, and the need goes away with
> C23
> anyway.

Removed.

I also made the pg_config.h.in changes and ran autoconf.

Regards,
    Jeff Davis


Attachment

pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part
Next
From: Thomas Munro
Date:
Subject: Re: C11: should we use char32_t for unicode code points?