-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/03/2012 08:16 AM, John Cowan wrote: > Alaric Snell-Pym scripsit: > >> I think it's worth mentioning that if the implementation supports >> exciting beyond-ASCII (not just Unicode) digits, their numeric >> value (as defined in whatever standard defines the character set, >> such as the Unicode numeric value proprety) needs to be supported >> by the implementation, for consistency. > > AFAIK only Unicode has any concept of the decimal-digit value > property, and no other character set supports any digits other than > the European (ASCII) set.
Yeah, that's just future-proofed wording as we already have the idea of non-Unicode characters lurking around. >> char-numeric? certainly seems to be of limited use without it, but >> is the char-numeric?/digit-value pair actually useful at all in the >> scope of WG1, given string->number? > > Unless we are to extend `string->number` to handle non-European > digits (and then `read`, and then numeric literals?), I think so. > Well, if digit-value exists and handles all those fun cases, then I think that read (and, therefore by definition, numeric literals), should do so too for consistency and to avoid having to have two parallel digit->number conversions lurking inside every implementation, one a subset of the other. ABS - -- Alaric Snell-Pym http://www.snell-pym.org.uk/alaric/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/ysjIACgkQRgz/WHNxCGqlMgCfZqVEukHdec+hYb0FLKOpzLUG blcAnjQkYmCvm5WC2SF9CALnoVJ0p0MZ =MHxR -----END PGP SIGNATURE----- _______________________________________________ Scheme-reports mailing list [email protected] http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports
