[racket-dev] `configure-runtime' submodule

2013-05-07 Thread Matthew Flatt
When you run #lang racket '#(1 1 1) the output is '#(1 1 1) When you run #lang scheme '#(1 1 1) the output is #(1 1 1) The difference in output (i.e., whether there's a leading quote) is because the `racket' and `scheme' languages arrange different run-time configuration of printin

Re: [racket-dev] `configure-runtime' submodule

2013-05-07 Thread Jay McCarthy
On Tue, May 7, 2013 at 7:17 AM, Matthew Flatt wrote: > The `racket' (and `racket/base') language adds a > `configure-runtime' submodule to a module body unless there's already > an immediate declaration (i.e., not under `begin' and not introduced by > a macro). Does that mean that if it *is* unde

Re: [racket-dev] `configure-runtime' submodule

2013-05-07 Thread Matthew Flatt
At Tue, 7 May 2013 07:31:36 -0600, Jay McCarthy wrote: > On Tue, May 7, 2013 at 7:17 AM, Matthew Flatt wrote: > > The `racket' (and `racket/base') language adds a > > `configure-runtime' submodule to a module body unless there's already > > an immediate declaration (i.e., not under `begin' and not

[racket-dev] JIT question

2013-05-07 Thread Jon Zeppieri
I realize that I should get a --disable-jit version running before tackling this, but since I stumbled into it last night... In jitinline.c, at line 1834, there is code for generating a JIT-ted version of char->integer. I think I understand all of it, except for line 1851: 1851: jit_movr_p(dest,

Re: [racket-dev] JIT question

2013-05-07 Thread Matthew Flatt
I think you're right: line 1851 is useless. I added line 1851 weeks after writing the surrounding code. At the time that I added line 1851, the real repair was changing line 1859 to use `dest' as the destination. I didn't pay enough attention to see that the slow path is a failure path, so no resu

Re: [racket-dev] JIT question

2013-05-07 Thread Jon Zeppieri
Thank you! On Tue, May 7, 2013 at 5:37 PM, Matthew Flatt wrote: > I think you're right: line 1851 is useless. > > I added line 1851 weeks after writing the surrounding code. At the time > that I added line 1851, the real repair was changing line 1859 to use > `dest' as the destination. I didn't p