Front page | perl.perl5.porters |
Postings from September 2002
On Mon, 30 Sep 2002, Michael G Schwern wrote: > A JIT is a much more clear-cut in the Java world because they actually have > seperate compile (javac) and run (java) steps. So the Java JIT is a > physically seperate thing and its big deal for them because they didn't have > one for so long. Having two steps to run a program is so 1980. ;) I don't think that's quite right. Java programs that use JITs still use a separate compilation phase. The first compilation phase transforms Java code into Java bytecode. The JIT transforms Java bytecode into native machine code "just in time" for the machine to execute it. This means that instead of an interpreter loop running over bytecode (like Perl) you get an actual machine-code representation of your Java program running directly on the CPU. For an example of a JIT in Perl, see HTML::Template::JIT. It uses Inline::C to turn templates into machine code "just in time" to execute them. Ultimately "JIT" is a rather loose term. It's more like an adjective that you can use to describe a compiler than a proper-noun in and of itself. -samThread Previous | Thread Next