Date: Wed, 26 Nov 2025 09:55:56 -0800
On Wednesday, 26 November 2025 08:27:39 Pacific Standard Time David Brown
wrote:
> > Would that make the 512-bit integer the "ludicrously long" and 1024 go
> > "plaid"? :-)
>
> We are onto "Space Balls The Movie" now, aren't we? Can we look up the
> VHS version of C++29 to see how it all ends? :-)
Oh, why didn't we think of just fast-forwarding!
> I remember reading an April Fool's proposal for adding new integer sizes
> to C, using combinations of "long" and "short" to get different sizes -
> like a "short long int" would be 24 bits. Unfortunately I am unable to
> find it again.
https://wg21.link/p0989 - Standardizing Extended Integers
short long int j; // (1 + 1/0.5)(32) = 48 bits
short int -> 16 bits
long short int -> 24 bits
long long short int -> 28 bits
long long long short int -> 30 bits
wrote:
> > Would that make the 512-bit integer the "ludicrously long" and 1024 go
> > "plaid"? :-)
>
> We are onto "Space Balls The Movie" now, aren't we? Can we look up the
> VHS version of C++29 to see how it all ends? :-)
Oh, why didn't we think of just fast-forwarding!
> I remember reading an April Fool's proposal for adding new integer sizes
> to C, using combinations of "long" and "short" to get different sizes -
> like a "short long int" would be 24 bits. Unfortunately I am unable to
> find it again.
https://wg21.link/p0989 - Standardizing Extended Integers
short long int j; // (1 + 1/0.5)(32) = 48 bits
short int -> 16 bits
long short int -> 24 bits
long long short int -> 28 bits
long long long short int -> 30 bits
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Principal Engineer - Intel Data Center - Platform & Sys. Eng.
Received on 2025-11-26 17:55:58
