From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Jeff Davis <pgsql(at)j-davis(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter(at)eisentraut(dot)org> |
Subject: | Re: cpluspluscheck vs ICU |
Date: | 2023-08-07 23:35:57 |
Message-ID: | 20230807233557.rhxwxmvofxtzkavy@awork3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2023-03-10 20:10:30 -0800, Andres Freund wrote:
> On 2023-03-10 19:37:27 -0800, Andres Freund wrote:
> > I just hit this once more - and I figured out a fairly easy fix:
> >
> > We just need a
> > #ifndef U_DEFAULT_SHOW_DRAFT
> > #define U_DEFAULT_SHOW_DRAFT 0
> > #endif
> > before including unicode/ucol.h.
> >
> > At first I was looking at
> > #define U_SHOW_CPLUSPLUS_API 0
> > and
> > #define U_HIDE_INTERNAL_API 1
> > which both work, but they are documented to be internal.
>
> Err. Unfortunately only the U_SHOW_CPLUSPLUS_API approach actually works. The
> others don't, not quite sure what I was doing earlier.
>
> So it's either relying on a define marked as internal, or the below:
>
> > Alternatively we could emit U_DEFAULT_SHOW_DRAFT 0 into pg_config.h to avoid
> > that issue.
> >
> >
> > The only other thing I see is to do something like:
> > [ugly]
> > which seems mighty ugly.
The ICU docs talk about it like it's not really internal:
https://github.com/unicode-org/icu/blob/720e5741ccaa112c4faafffdedeb7459b66c5673/docs/processes/release/tasks/healthy-code.md#test-icu4c-headers
So I'm inclined to go with that solution.
Any comments? Arguments against?
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2023-08-07 23:54:10 | Re: Support to define custom wait events for extensions |
Previous Message | Michael Paquier | 2023-08-07 23:25:49 | Re: Fix badly generated entries in wait_event_names.txt |