Re: PRI?64 vs Visual Studio (2022)

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Bryan Green <dbryan.green@gmail.com>

Cc: pgsql-hackers@lists.postgresql.org

Date: 2025-12-15T20:39:17Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Test PRI* macros even when we can't test NLS translation.
- 462e2476525e 19 (unreleased) landed
Avoid requiring Spanish locale to test NLS infrastructure.
- 7db6809ced44 19 (unreleased) landed
Drop support for MSVCRT's float formatting quirk.
- 6b46669883fa 19 (unreleased) landed
Drop support for MSVCRT's %I64 format strings.
- 7ab9b34614c2 19 (unreleased) landed
Use PRI?64 instead of "ll?" in format strings (continued).
- a0ed19e0a9ef 18.0 cited
Use <stdint.h> and <inttypes.h> for c.h integers.
- 962da900ac8f 18.0 cited
Make float exponent output on Windows look the same as elsewhere.
- f1885386f624 12.0 cited

I wrote:
> Experimenting here, it looks like 'C.UTF-8' might be accepted
> everywhere.  I even got it to pass on Solaris's not-GNU gettext,
> which I thought for sure would be the weak spot in the idea.
> I'll press forward with that.

Hmmm ... the first batch of BF reports show that on some Linux
machines, it works to set lc_messages to 'C.UTF-8', but nonetheless
no translation happens.  Did you notice any other gating factors?

			regards, tom lane