Email list hosting service & mailing list manager

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 13 Apr 2019 07:27 UTC

> While the common in-use cases are ..., +, and - , R7RS permits lots of symbols starting with decimal point or sign.   See <peculiar identifier>.
>
> ...and underscore is part of <special initial> which makes it part of <dot subsequent> and <sign subsequent> too.
>
> While adding a bunch of tests just now, I came across the fact that reading "._75" has to produce a symbol and not the inexact number 0.75, but ".7_5" is okay.

> Incidentally, MIT Scheme has allowed 1+ (for the increment-by-one procedure) and -1+ (for the decrement-by-one procedure) for forever.

> So yes. numbers can't have leading underscores, and 1+ and -1+ are
> implementation-specific additions to the <peculiar identifier> list.

Very good points all.

Let us take peculiar identifiers and implementation-specific additions
into account and assume the most conservative proposal (an underscore
can only appear between two digits -- no leading, trailing or duplicated
underscores). Do you feel that the proposal is still reasonable or have
we blown our complexity budget?

I'm starting to realize why Common Lisp reserving "potential numbers"
from the get-go was a wise move. (Though they specified it so that
potential numbers parse as symbols in implementations which can't handle
them, which may not have been as wise.)