On May 5, 2010, at 4:12 AM, Shlomi Fish wrote: > On Wednesday 05 May 2010 10:25:48 Craig DeForest wrote: >> >> IDL's interpreter, on the other hand, really blows chunks compared to >> Perl's. It's not legally possible to know what IDL is doing, but I >> suspect it merely tokenizes, rather than JIT-compiling, the >> interpreted code, so the interpreter has to do a lot more work at >> run- >> time (work that Perl caches up-front). > > Just a nitpick - perl 5 does not do JIT-compilation either. In JIT > compilation > one converts the internal bytecode (also called P-code) to machine > language at > run-time so it will later execute faster. That's what the JVM and > the .NET CLR > are doing, but perl 5 (the Perl 5 implementation) does not do it, at > least not > yet. See:
Hmmm, Perl does compile to byte-code, which is faster to execute than tokenized source code. The compilation to byte-code happens at run time, which is why I called it JIT. But I see your point. _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
