[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Scheme-reports] [scheme-reports-wg1] Unintended consequences of #319

On Wed, Apr 11, 2012 at 2:59 AM, John Cowan <cowan@x> wrote:
> Ticket #319, which requires that `string->number`, `read`, and the program
> reader used by the implementation all impose the same restrictions,
> if any, on reading numbers, was adopted by the WG on the fifth ballot.

I think you mean #327.

> On my reading of it, this means that the R5RS permission for
> `string->number` to return #f if its argument has a radix prefix is
> inconsistent with this decision (since "#x10" must work in code, it must
> work in `string->number` as well), and I have withdrawn it accordingly:

R5RS doesn't have such permission - it has permission
to return #f when the string has _any_ radix prefix, and
in a number of other cases related to incomplete numeric
towers.  What we explicitly voted on is that these must
be unified with `read` behavior.  I don't think this is an
unintended consequence.


Scheme-reports mailing list