Opened 5 years ago

Closed 5 years ago

#327 closed defect (fixed)

Specify that read, the program reader, and string->number accept the same syntax

Reported by: cowan Owned by: cowan
Priority: major Milestone:
Component: WG1 - Core Keywords:
Cc:

Description (last modified by cowan)

Currently there is no guarantee of this.

Possibilities:

All the same: The lexical syntax for numbers accepted by string->number and read, as well as the corresponding syntax of literal numbers in programs, must be the same.

All the same at run time: The lexical syntax for numbers accepted by string->number and read must be the same, but the relationship with the the corresponding syntax of literal numbers in programs is unspecified.

All potentially different: The relationships between lexical syntax for numbers accepted by string->number and read, as well as the corresponding syntax of literal numbers in programs, is unspecified.

Change History (4)

comment:1 Changed 5 years ago by cowan

  • Description modified (diff)

More from Vincent:

The syntactic issues relate to such things as whether S, F, D, and L are valid ("the implementation may accept...", p. 32). Pragmatic issues include whether integer or other literals might overflow (on a bignum-less implementation), whether or not the implementation applies the same restrictions, described at the bottom of p. 37) to string->number, read, and literals in source programs; the default precision if the E exponent marker is used; and numerical roundoff on input conversion (whether, e.g., (= (string->number? 0.1) 0.1) is defined to be true).

Vincent formerly supported the All the same choice, but now supports All the same at run time.

comment:2 Changed 5 years ago by cowan

  • Status changed from new to decided

The WG voted to adopt this proposal.

comment:3 Changed 5 years ago by cowan

  • Owner changed from alexshinn to cowan
  • Status changed from decided to writing

comment:4 Changed 5 years ago by cowan

  • Resolution set to fixed
  • Status changed from writing to closed

That is, we adopted the proposal that all three support the same syntax.

Note: See TracTickets for help on using tickets.