| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Japin Li <japinli(at)hotmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Cannot find a working 64-bit integer type on Illumos |
| Date: | 2024-07-14 14:51:54 |
| Message-ID: | 2779385.1720968714@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
> On 04.07.24 03:55, Thomas Munro wrote:
>>> Personally, I find "PRId64" pretty unreadable. "INT64_MODIFIER" wasn't
>>> nice either, though, and following standards is good, so I'm sure I'll
>>> get used to it.
> Using PRId64 would be very beneficial because gettext understands it,
> and so we would no longer need the various workarounds for not putting
> INT64_FORMAT into the middle of a translated string.
Uh, really? The translated strings live in /usr/share, which is
expected to be architecture-independent, so how would they make
that work?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Lakhin | 2024-07-14 16:00:00 | Re: Internal error codes triggered by tests |
| Previous Message | Peter Eisentraut | 2024-07-14 14:47:50 | Re: Cannot find a working 64-bit integer type on Illumos |