That's true, and Guile and Chicken do accept that notation, but they treat the #s as zeros; I can't believe any implementation does anything different.  They are not in R[67]RS, and even Scheme 9, which is supposed to be a full R4RS implementation, doesn't support them.   I doubt if very many programs, if any, actually contain such literals.

Do you know if that "all Schemes installed" Docker image ever get set up?  If so I could run another comprehensive test.

On Mon, Nov 18, 2019 at 12:57 PM Lassi Kortela <xxxxxx@lassi.io> wrote:
> An inexact integer is just an inexact number that happens to have an
> integral value (like 12.0), so there's nothing wrong with that.  In
> principle, inexact numbers don't have to be floats (they could be, say
> decimal numbers with 10 integral digits and 3 fractional digits), but
> the whole reason inexact numbers exist in Scheme is efficiency (exact
> arithmetic can get very slow if you do a lot of divisions).  So since
> floats are provided in all modern hardware, Scheme models that.

I thought there was something more complex going on in pre-R6RS Scheme
standards, as discussed in
<https://stackoverflow.com/questions/10935110/meaning-of-in-scheme-number-literals/>.
That page shows some integers where the integer part has ## unknown
digit markers.

It's probably pedantic to be clearing this up nowadays, but I thought to
err on the safe side and ask.