Re: What's the rationale for considering "0x1.max" as invalid ?

[Alex Parrill via Digitalmars-d-learn]

On Tuesday, 5 April 2016 at 19:00:43 UTC, Basile B. wrote:

0x1.max // exponent expected in hex float
0x1 .max // OK
1.max // OK

What's the ambiguity when it's an hex literal ?

It's potentially ambiguous with hexadecimal floating point numbers

0xdeadbeef.p5 // hex float or hex int + method?

dlang.org/spec/lex.html#HexFloat