Great!
On Sat, May 11, 2013 at 2:11 PM, Jon Zeppieri <zeppi...@gmail.com> wrote: > Ok, I fixed this problem. I had just left out tests for immediates in > a number of places. I think I was confused because certain expressions > like > > (syntax? #\c) > > ... seemed to be working just fine, but I think they were not actually > working in the JIT. I suspect they were constant-folded before even > getting there. > > Thanks for your help, Matthew and Robby. > > -Jon > > > > On Sat, May 11, 2013 at 1:56 PM, Jon Zeppieri <zeppi...@gmail.com> wrote: > > Something to do with syntax, I think, but I'm not sure what: > > > >> (datum->syntax #f #\c) > > #<syntax #\c> > > > >> ((current-prompt-read)) > >> #\c > > #<syntax::25 #\c> > > > >> (read-syntax) > > #\c > > #<syntax::15 #\c> > > > >> (syntax #\c) > > Segmentation fault: 11 > > > >> (quasisyntax #\c) > > Segmentation fault: 11 > > > > They all work when the JIT is disabled. > > > > -Jon > > > > > > > > On Sat, May 11, 2013 at 1:32 PM, Jon Zeppieri <zeppi...@gmail.com> > wrote: > >> On Sat, May 11, 2013 at 1:31 PM, Robby Findler > >> <ro...@eecs.northwestern.edu> wrote: > >>> Relatedly, does this crash? > >>> > >>> (parameterize ([current-input-port (open-input-string "#\\c")]) > >>> (read-eval-print-loop)) > >> > >> Yes, it does. I will take a look at the code in misc.rkt. Thanks! > >> > >> -Jon >
_________________________ Racket Developers list: http://lists.racket-lang.org/dev
