Treat float literals as decimal float literals and not as binary float literals about xl

[c3d]

Interesting idea. I wonder if the problem is not what default representation for real, ie should it be binary or decimal. Note that decimal FP has other issues (e.g. correct rounding I believe is more difficult).

[dumblob]

I wonder if the problem is not what default representation for real, ie should it be binary or decimal.

I'd definitely go also for decimal FP as I feel it must not be "worse than float". But thinking of it there are at least two ideas to explore:

1. real could actually be made even closer to mathematical notation used "on a paper" by introducing something like a "variable" decimal FP in a sense that one would choose beforehand how many "true" significant digits incl. zeros (not to be confused with decimal places nor with "usual" significant digits) should be used for output (e.g. a literal 1.500 would have 4 significant digits, 0001.500 would have 4 significant digits, 300 -> 3 sigdigits, 0.000100 -> 7 sigdigits) and internally a higher precision would be used to account for few rounding errors whereas float would stay compatible with IEEE 754 and thus support only _Decimal32 _Decimal64 _Decimal128 variants under the hood.

2. leave float as binary floating point and make only real into decimal floating point (possibly with the significant digits extension for better user experience and output purposes)

Note that decimal FP has other issues (e.g. correct rounding I believe is more difficult).

Could you be more specific? It still has infinity (actualy many infinities and both negative and positive ones) but otherwise most (if not all) of the issues I know of are basically gone. Actually correct rounding of decimal FP is one of the reasons why decimal FP is being used over binary FP. Feel free to take a look at the "best" library emulating decimal FP to see how rounding is being done (btw. mpdecimal is being used also by Python etc.).