Sujet : Re: do { quit; } else { }
De : david.brown (at) *nospam* hesbynett.no (David Brown)
Groupes : comp.lang.cDate : 13. Apr 2025, 19:53:03
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vth16f$3g7ar$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
User-Agent : Mozilla Thunderbird
On 13/04/2025 19:57, Michael S wrote:
On Fri, 11 Apr 2025 11:15:44 -0700
Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:
bart <bc@freeuk.com> writes:
[...]
8 A u64 type can be denoted as either 'uint64_t' OR as some
combination of the tokens (long, long, unsigned, [int])
>
"uint64_t" and "unsigned long long int" do not mean the same thing.
>
And it's a PITA.
There is only one thing I find a little bit annoying about the sized integer types in C - the printf specifiers. I tend to "cheat" with these, using "%lu" for uint32_t on the targets I usually use, where I know uint32_t is "long unsigned int". Other than that, I stick to the size-specific types for much of my code except local "throw-away" variables that might be "int". Compatibility or lack thereof between the size-specific types and the standard integer types is simply irrelevant in my code.