Jonathan E. Paton: # > How about the JIT engine then. # # JIT runs on bytecode, producing bytecode.
No, JIT runs on bytecode, producing equivalent machine code. # > When does parrot use it? # # Before executing bytecode. # # > how well does it scale? ( has anyone done some benchmarking ) # # Don't ask me :P If you haven't already, then you'd # be best looking at the background information at: # # http://dev.perl.org/perl6 # # you should get the basics there. Apparently each Parrot # source file comes with a .dev file... to tell you what's # been done - the implementation notes. No, it's *supposed* to come with a .dev file. It doesn't yet. :^) Honestly, the JIT is Really Deep Magic and basically a special case in the code. I usually pretend it doesn't exist, because I don't know assembly and it's confusing. JIT people--anyone want to answer this guy's question? --Brent Dax <[EMAIL PROTECTED]> @roles=map {"Parrot $_"} qw(embedding regexen Configure) #define private public --Spotted in a C++ program just before a #include
