Re: Inconsistency in `string-to-number'

[Juanma Barranquero]

> Which is why I thing we should fix it the other way around: to
> recognize "1.2:" as a number. That cannot possibly break anything, so
> it should be safe to do before the release, IMO.

It's a long shot, but there could conceivably be code that relies in
truncation of "float + non-space", i.e., that expects ("1.2:" => 1).
So it's not true that it cannot possibly break anything; just
unlikely.

Yes, code that relies on "1.2:" => 1 is abusing a non-documented
quirk; but code that relies on "1:" => 1 is also doing the same thing.

(That said, I'm not going to push for one behavior over the other.)

    Juanma