Oops! I have to take back my complaint that R3RS underspecifies the interrelationships among values returned by CHAR->INTEGER for numeric characters. JAR pointed out to me that you can just compute a table in which to look up the values (indexed by the CHAR->INTEGER result). It wastes some space, but so what. Now my reader is completely (?) portable under R3RS. -Mark