This is mentioned.
> machine dependent integer widths
What exactly do you dislike about this?
This is mentioned.
> machine dependent integer widths
What exactly do you dislike about this?
It becomes less important as we all converge on 64-bit machines with 32-bit "int" types, but it's still a monumental pain point for portability.
Or what do you even do about it?
A handful of solutions already exist: - Use a higher-level language - Java
All you need is a list of what width each type is.
> A handful of solutions already exist: - Use a higher-level language - Java
It doesn't require being "higher level". If anything it pushes code to a slightly lower level.
This is exactly the kind of minutiae that GP was bemoaning.
> If anything it pushes code to a slightly lower level
Yeah by way of higher-level abstractions ...
How is this “minutiae”? You should always know the possible range of a numeric variable or field when you create it, so why not just write what size it is? In Rust the main numeric types look like this: i32, u64, u8. You just pick the one you want.
These typedefs as I'm used to them do address cross-platform issues.
Storage classes are "minutiae" however when all you want is just a straight up number.
Python gives me an Integer type when I want a whole number, or a Float when I want to represent partials.
I don't really care to be honest how that gets represented in memory in this case.
> Storage classes are "minutiae" however when all you want is just a straight up number.
You can have a single "straight up number" and mention the bit width in the language spec. The mere act of writing it down doesn't force coders to deal with any more minutiae than they already had to deal with.
> Yeah by way of higher-level abstractions ...
I strongly object to this. "float is at least x bits" and "float is exactly x bits" are the same level of abstraction, and almost every language, high or low level, picks one of those options.
Also you named Java as being on the easy side and that has four different integer sizes...
Double doesn't behave like a whole number.
java only has a single int type, which is 32-bit regardless of machine architecture.
I was suggesting double for your partials, not your whole numbers.
> java only has a single int type, which is 32-bit regardless of machine architecture.
I'm so confused.
You said having a "list of what width each type is" is bad because it forces the user to deal with "minutiae".
But that's exactly what Java does. int is 32 bits, short is 16, long is 64
And then you praise a type in Python that does the same thing as "double" in C. It's usually 64 bits, but it might be something else.