Date: Sun, 28 Jul 2024 11:41:43 +0200
This may help: https://en.cppreference.com/w/cpp/types/integer
On 7/28/2024 11:08 AM, Pynix Wnag via Liaison wrote:
> any plan to make stdint types into language and compiler, modern
> languages use width in type names, int8, int16, int32,
> int64,uint8,uint16,uint32,uint64.
> when I learn c language first time, I must try to remember short long
> bit width.
> why not use types with bit width?
> no one want to remember usb version names, full speed, high
> speed,ultra speed, what we want is usb 5g, usb10g, usb20g, usb40g.
>
> I always ask myself, how long “long” is, how short “short” is.
> if we need 128 bit, how we call it, long long? double long?
>
> _______________________________________________
> Liaison mailing list
> Liaison_at_[hidden]
> Subscription: https://lists.isocpp.org/mailman/listinfo.cgi/liaison
> Link to this post: http://lists.isocpp.org/liaison/2024/07/1463.php
On 7/28/2024 11:08 AM, Pynix Wnag via Liaison wrote:
> any plan to make stdint types into language and compiler, modern
> languages use width in type names, int8, int16, int32,
> int64,uint8,uint16,uint32,uint64.
> when I learn c language first time, I must try to remember short long
> bit width.
> why not use types with bit width?
> no one want to remember usb version names, full speed, high
> speed,ultra speed, what we want is usb 5g, usb10g, usb20g, usb40g.
>
> I always ask myself, how long “long” is, how short “short” is.
> if we need 128 bit, how we call it, long long? double long?
>
> _______________________________________________
> Liaison mailing list
> Liaison_at_[hidden]
> Subscription: https://lists.isocpp.org/mailman/listinfo.cgi/liaison
> Link to this post: http://lists.isocpp.org/liaison/2024/07/1463.php
Received on 2024-07-28 09:41:50