Path: csiph.com!news.swapon.de!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups: comp.lang.c
Subject: Re: #include <stdint.h>
Date: Mon, 14 Jun 2021 01:24:26 -0700
Organization: None to speak of
Lines: 17
Message-ID: <87o8c8yhtx.fsf@nosuchdomain.example.com>
References: <sa5vrs$7d3$1@dont-email.me> <87wnqxxoe3.fsf@nosuchdomain.example.com> <sa6vaf$4r0$2@solani.org>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: reader02.eternal-september.org; posting-host="424da5ba9f7e7fcac70b5d6e5f55a732"; logging-data="24087"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/N2z9rWywba4qFjH3OpuDN"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Cancel-Lock: sha1:Fd5PKJzTsgwM8Vd1KNcWnTlY70U= sha1:T/883uMTu7da2clTyPUHrNpWWhc=
Xref: csiph.com comp.lang.c:161432

Philipp Klaus Krause <pkk@spth.de> writes:
> Am 14.06.21 um 02:48 schrieb Keith Thompson:
>> If you have an integer type that might possibly be wider than long
>> long (which is unlikely in practice), you can convert to intmax_t
>> or uintmax_t and use "%jd" or "%ju".  That might be overkill if you
>> don't really need 100% guarantee portability.
>
> And there is the real risk of intmax_t being removed from a future
> standard, which is very, very unlikely to ever happen to long long.

I doubt that there's much risk of that.  I can imagine its semantics
being changed, but removing it would break existing code.

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips Healthcare
void Void(void) { Void(); } /* The recursive call of the void */