Date: Wed, 26 Nov 2025 21:52:28 +0100
On 26/11/2025 18:55, Thiago Macieira wrote:
> 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
>
That's the one! Thank you - I've been trying to find that for a while.
David
> 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
>
That's the one! Thank you - I've been trying to find that for a while.
David
Received on 2025-11-26 20:52:35
