This site is a static rendering of the Trac instance that was used by R7RS-WG1 for its work on R7RS-small (PDF), which was ratified in 2013. For more information, see Home.

Source for ticket #164

cc

changetime

2012-10-05 12:39:55

component

WG1 - Core

description

The current draft, like R6RS, defines `char-numeric?` according to the nonexistent Unicode Numeric property.  That has to be fixed.  Options:

 1. `char-numeric?` returns `#t` if the character's Numeric_Type property value is other than `None`.  This means that many hanzi are both alphabetic and numeric.

 2. (Omitted, because it does not preserve IEEE Scheme)

 3. Define `char-numeric?` to return `#t` only for 0, 1, 2, 3, 4, 5, 6, 7, 8, and 9.  This retains compatibility witht R5RS, and we can still use `char-numeric?` to parse numbers, and safely use `(- (char->integer c) (char->integer #\0))` to obtain the digit value the character represents.  (Note: R5RS programs that use `char-numeric?` to parse numbers will break if we adopt the current draft's definition of `char-numeric?`).  Gauche, Gambit, and Chicken (without the utf8 egg) work like this.

 4. Define `char-numeric?` as equivalent to the Numeric_Digit property (general category value of Nd).  Guile 2.0, Kawa, Larceny, Ypsilon, Mosh, and IronScheme work like this.

 5. define `char-numeric?` as equivalent to the Number property (general category values of Nd, Nl, No).  Scheme48, Chez, and Ikarus work like this.

id

keywords

milestone

owner

cowan

priority

major

reporter

cowan

resolution

fixed

severity

status

closed

summary

Meaning of char-numeric?

time

2011-04-28 09:56:34

type

defect

Changes

Change at time 2012-10-05 12:39:55

author

cowan

field

comment

newvalue

oldvalue

raw-time

1349415595668434

ticket

time

2012-10-05 12:39:55

Change at time 2012-10-05 12:39:55

author

cowan

field

resolution

newvalue

fixed

oldvalue

raw-time

1349415595668434

ticket

time

2012-10-05 12:39:55

Change at time 2012-10-05 12:39:55

author

cowan

field

status

newvalue

closed

oldvalue

writing

raw-time

1349415595668434

ticket

time

2012-10-05 12:39:55

Change at time 2011-07-11 04:45:25

author

cowan

field

comment

newvalue

oldvalue

raw-time

1310334325000000

ticket

time

2011-07-11 04:45:25

Change at time 2011-07-11 04:45:25

author

cowan

field

owner

newvalue

cowan

oldvalue

alexshinn

raw-time

1310334325000000

ticket

time

2011-07-11 04:45:25

Change at time 2011-07-11 04:45:25

author

cowan

field

status

newvalue

writing

oldvalue

decided

raw-time

1310334325000000

ticket

time

2011-07-11 04:45:25

Change at time 2011-07-10 18:19:08

author

alexshinn

field

comment

newvalue

We voted for the Numeric_Digit property.

oldvalue

raw-time

1310296748000000

ticket

time

2011-07-10 18:19:08

Change at time 2011-07-10 18:19:08

author

alexshinn

field

resolution

newvalue

oldvalue

raw-time

1310296748000000

ticket

time

2011-07-10 18:19:08

Change at time 2011-07-10 18:19:08

author

alexshinn

field

status

newvalue

decided

oldvalue

new

raw-time

1310296748000000

ticket

time

2011-07-10 18:19:08

Change at time 2011-04-28 09:58:07

author

cowan

field

comment

newvalue

oldvalue

raw-time

1303959487000000

ticket

time

2011-04-28 09:58:07

Change at time 2011-04-28 09:58:07

author

cowan

field

description

newvalue

The current draft, like R6RS, defines `char-numeric?` according to the nonexistent Unicode Numeric property.  That has to be fixed.  Options:

 1. `char-numeric?` returns `#t` if the character's Numeric_Type property value is other than `None`.  This means that many hanzi are both alphabetic and numeric.

 2. (Omitted, because it does not preserve IEEE Scheme)

 3. Define `char-numeric?` to return `#t` only for 0, 1, 2, 3, 4, 5, 6, 7, 8, and 9.  This retains compatibility witht R5RS, and we can still use `char-numeric?` to parse numbers, and safely use `(- (char->integer c) (char->integer #\0))` to obtain the digit value the character represents.  (Note: R5RS programs that use `char-numeric?` to parse numbers will break if we adopt the current draft's definition of `char-numeric?`).  Gauche, Gambit, and Chicken (without the utf8 egg) work like this.

 4. Define `char-numeric?` as equivalent to the Numeric_Digit property (general category value of Nd).  Guile 2.0, Kawa, Larceny, Ypsilon, Mosh, and IronScheme work like this.

 5. define `char-numeric?` as equivalent to the Number property (general category values of Nd, Nl, No).  Scheme48, Chez, and Ikarus work like this.

oldvalue

The current draft, like R6RS, defines `char-numeric?` according to the nonexistent Unicode Numeric property.  That has to be fixed.  Options:

 1. `char-numeric?` returns `#t` if the character's Numeric_Type property value is other than `None`.  This means that many hanzi are both alphabetic and numeric.

 2. (Omitted, because it does not preserve IEEE Scheme)

 3. Define char-numeric? to return #t only for 0, 1, 2, 3, 4, 5, 6, 7, 8, and 9.  This retains compatibility witht R5RS, and we can still use `char-numeric?` to parse numbers, and safely use `(- (char->integer c) (char->integer #\0))` to obtain the digit value the character represents.  (Note: R5RS programs that use `char-numeric?` to parse numbers will break if we adopt the current draft's definition of `char-numeric?`).  Gauche, Gambit, and Chicken (without the utf8 egg) work like this.

 4. Define `char-numeric?` as equivalent to the Numeric_Digit property (general category value of Nd).  Guile 2.0, Kawa, Larceny, Ypsilon, Mosh, and IronScheme work like this.

 5. define `char-numeric?` as equivalent to the Number property (general category values of Nd, Nl, No).  Scheme48, Chez, and Ikarus work like this.

raw-time

1303959487000000

ticket

time

2011-04-28 09:58:07