Jeffrey Read's ballot is now posted to WG1BallotRead. He writes:
# NaN-ness should be contagious: if any component of a numeric value # is NaN, then the whole thing is "not a number". Accordingly complex # numbers with one part NaN should be either forbidden, or nan? returns #t # on them but not any predicates that apply to is-a-number numeric values. Not allowing half-NaNs would seriously alienate the numerical users community. We don't want to go there. In #425 Add read-string, read-string!, write-string procedures to (scheme base), he asks: # How would encodings be handled? In the same way as the rest of WG1: default encodings and encoding control are implementation-dependent. I have a WG2 proposal to provide detailed mechanisms for encoding control: see FilesAdvancedCowan and SettingsListsCowan if you are interested in the details. -- One art / There is John Cowan <[email protected]> No less / No more http://www.ccil.org/~cowan All things / To do With sparks / Galore --Douglas Hofstadter _______________________________________________ Scheme-reports mailing list [email protected] http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports
