Follow-up Comment #4, bug #31680 (project guile): On Thu 18 Nov 2010 20:45, Göran Weinholt <[email protected]> writes:
> (define modp-group1-p > (string->number > "FFFFFFFFFFFFFFFFC90FDAA22168C234C4C6628B80DC1CD1 > 29024E088A67CC74020BBEA63B139B22514A08798E3404DD > EF9519B3CD3A431B302B0A6DF25F14374FE1356D6D51C245 > E485B576625E7EC6F44C42E9A63A3620FFFFFFFFFFFFFFFF" > 16)) Sounds legit. > surely you should not need to check for U+205F and so on explictly, > isn't it enough to see that they belong to the right > char-general-category? I think the deal is that all (?) of the other escapes can be dealt with via the equivalent of a `case' expression. This one requires a property lookup. It's not as nice. Also note the thread at http://lists.r6rs.org/pipermail/r6rs-discuss/2010-November/006146.html. Is there a use case for allowing intraline spaces before the newline? Disallowing that would eliminate a state in the parser. Andy _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?31680> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
