At Mon, 23 Jun 2014 10:45:44 -0400, Sam Tobin-Hochstadt wrote: > On Mon, Jun 23, 2014 at 8:29 AM, <mfl...@racket-lang.org> wrote: > > > > 6a5a303 Matthew Flatt <mfl...@racket-lang.org> 2014-06-23 13:23:47 +0100 > > : > > | avoid getting stuck on non-UTF-8 symbol encodings in bytecode > > | > > > Does this fix apply to keywords as well?
Yes. > I assume that strings are handled differently. Yes, but now that I look closely, the "fuzz.rkt" test was getting stuck while deciding whether to use vertical-bar quoting when printing a symbol (in an error message, I assume). I didn't fix the reading of symbols, which means that I fixed a downstream symptom instead of the source of the problem. The problem remains that a ".zo" could provide an invalid UTF-8 encoding for a symbol, and then something like `symbol->string` could go wrong. I'll push a repair to the bytecode reader so that it checks the encoding of symbols (which doesn't seem to slow it down measurably). _________________________ Racket Developers list: http://lists.racket-lang.org/dev
