Re: PRI?64 vs Visual Studio (2022)

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: PRI?64 vs Visual Studio (2022)
Date: 2025-11-19 02:50:44
Message-ID: CA+hUKGLzXzQcbjEHW08Z6g=mzBkpLtzSJ7Bt2S2XmxP1bwpq8A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 19, 2025 at 3:28 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I agree that starting to rely on PRI?64 in translatable strings
> is raising the bar a good deal, so maybe it's time to do something
> about that.

Perhaps meson/configure should do a po -> mo -> gettext() check with a
canned test message? That'd also make sure your msgfmt and libintl
are compatible, something I worried about when I wrote about musl
recently.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2025-11-19 02:55:07 Re: transformJsonFuncExpr pathspec cache lookup failed
Previous Message Peter Smith 2025-11-19 02:49:30 Re: [PATCH] Add pg_get_subscription_ddl() function