Underscores in numbers for legibility Lassi Kortela (12 Apr 2019 18:54 UTC)
Re: Underscores in numbers for legibility Arthur A. Gleckler (12 Apr 2019 19:02 UTC)
Re: Underscores in numbers for legibility Lassi Kortela (12 Apr 2019 19:08 UTC)
Re: Underscores in numbers for legibility Shiro Kawai (12 Apr 2019 19:33 UTC)
Re: Underscores in numbers for legibility Lassi Kortela (12 Apr 2019 19:46 UTC)
Re: Underscores in numbers for legibility Peter Bex (12 Apr 2019 19:55 UTC)
Re: Underscores in numbers for legibility Lassi Kortela (12 Apr 2019 20:01 UTC)
Re: Underscores in numbers for legibility Peter Bex (12 Apr 2019 20:08 UTC)
Re: Underscores in numbers for legibility Arthur A. Gleckler (12 Apr 2019 20:15 UTC)
Re: Underscores in numbers for legibility Lassi Kortela (12 Apr 2019 20:23 UTC)
Re: Underscores in numbers for legibility Lassi Kortela (12 Apr 2019 22:17 UTC)
Re: Underscores in numbers for legibility John Cowan (12 Apr 2019 22:28 UTC)
Re: Underscores in numbers for legibility Jim Rees (13 Apr 2019 00:04 UTC)
Re: Underscores in numbers for legibility Arthur A. Gleckler (13 Apr 2019 00:10 UTC)
Re: Underscores in numbers for legibility John Cowan (13 Apr 2019 03:14 UTC)
Re: Underscores in numbers for legibility Lassi Kortela (13 Apr 2019 07:27 UTC)
Re: Underscores in numbers for legibility John Cowan (13 Apr 2019 13:52 UTC)
Re: Underscores in numbers for legibility Arthur A. Gleckler (13 Apr 2019 14:26 UTC)
Re: Underscores in numbers for legibility Lassi Kortela (13 Apr 2019 14:40 UTC)
Re: Underscores in numbers for legibility John Cowan (13 Apr 2019 15:27 UTC)
Re: Underscores in numbers for legibility Peter Bex (13 Apr 2019 19:37 UTC)
Re: Underscores in numbers for legibility John Cowan (13 Apr 2019 19:47 UTC)
Re: Underscores in numbers for legibility Lassi Kortela (15 Apr 2019 09:32 UTC)
Re: Underscores in numbers for legibility Arthur A. Gleckler (15 Apr 2019 14:33 UTC)
Re: Underscores in numbers for legibility Lassi Kortela (15 Apr 2019 15:18 UTC)
Re: Underscores in numbers for legibility Arthur A. Gleckler (15 Apr 2019 15:49 UTC)
Re: Underscores in numbers for legibility Lassi Kortela (15 Apr 2019 20:16 UTC)
Re: Underscores in numbers for legibility Lassi Kortela (13 Apr 2019 19:53 UTC)
Re: Underscores in numbers for legibility Per Bothner (13 Apr 2019 16:01 UTC)
Re: Underscores in numbers for legibility Lassi Kortela (13 Apr 2019 16:10 UTC)
Re: Underscores in numbers for legibility Per Bothner (12 Apr 2019 19:41 UTC)
Re: Underscores in numbers for legibility Lassi Kortela (12 Apr 2019 19:47 UTC)
Re: Underscores in numbers for legibility Per Bothner (12 Apr 2019 20:27 UTC)
Re: Underscores in numbers for legibility Lassi Kortela (12 Apr 2019 21:07 UTC)
Re: Underscores in numbers for legibility John Cowan (12 Apr 2019 21:53 UTC)
Re: Underscores in numbers for legibility Lassi Kortela (12 Apr 2019 22:37 UTC)
Re: Underscores in numbers for legibility Per Bothner (13 Apr 2019 16:23 UTC)

Re: Underscores in numbers for legibility Lassi Kortela 12 Apr 2019 22:37 UTC

> I have no problem with allowing underscores, as long as they can't be
> initial in a number.  I think internal-only, single-only is the Right
> Thing, but *not* to force three digits, so that in India people can
> write numbers like 3_14_15_926 (read "three crore fourteen lakh fifteen
> thousand nine hundred and twenty-six" in Indian English).  I think it
> should work with or without base and exactness prefixes, and in any
> digit string including fractional-parts and complex or higher-order numbers.

Thank you for once again bringing the international perspective.

So basically any place in a number that you can now have a string of two
or more digits, you could have those same digits plus any number of
underscores in between. As long as there aren't two or more consecutive
underscores.

> Accepting quantities  (number + unit) is okay too, but we'd need some
> agreed-on internal representation of quantities with a constructor and
> accessors.

Units of measure are now one of the selling points of F# though I
presume Kawa's feature preceded it. Agree that they are complex enough
to deserve their own SRFI (though it's very good that we consider the
syntax implications early so we don't paint ourselves into a corner).