On Fri, Mar 9, 2012 at 5:59 AM, Thomas Chust <ch...@web.de> wrote: > Anyway, if one worries about the performance cost of constants inlined > at compile time versus constants inlined by the JIT, then using a > language as high-level as Racket may be a mistake.
Not really related to the rest of this discussion, but: If your impression of JIT compilers is formed by using languages like Java, C#, or JavaScript, then you may have the wrong impression about Racket's current JIT. Instead, Racket's JIT should be thought of as like an ahead-of-time compiler to machine code that runs only first time your function is called (or "just in time" :). In particular, it doesn't recompile hot functions, optimize based on dynamic information from running the program, or that sort of thing. Those are, of course, things that would be great to have in the VM, so hopefully we'll change this situation in the future. -- sam th sa...@ccs.neu.edu ____________________ Racket Users list: http://lists.racket-lang.org/users
