-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 28-12-11 13:18, Matthew Flatt wrote: > Thanks for all the new info! I don't think that it's a bytcode > problem. I start to wonder if it's in number parsing... > > On line 1102 of "src/racket/src/numstr.c", there's a call to > STRTOD(). Does it change anything if you wrap that call with calls > to scheme_push_c_numeric_locale() and > scheme_pop_c_numeric_locale(loc)?: > > { GC_CAN_IGNORE char *loc; loc = scheme_push_c_numeric_locale(); d > = STRTOD(ffl_buf, &ptr); scheme_pop_c_numeric_locale(loc); }
Hi Matthew, you're certainly on the right track. I tried starting drracket in this way: LC_ALL="en_US.UTF-8" drracket & and almost all symptoms were gone. Marijn -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk78JkIACgkQp/VmCx0OL2wedgCfSApHFEmJ6GojTYbTGg/fY4fz LjoAnREzYAr9VYv/BZyAJEWYNunWNK9s =1ZSi -----END PGP SIGNATURE----- _________________________ Racket Developers list: http://lists.racket-lang.org/dev