|There's more than one way to do things|
Precompiled perl...by Eyck (Priest)
|on Oct 27, 2004 at 09:02 UTC||Need Help??|
Eyck has asked for the
wisdom of the Perl Monks concerning the following question:
Most not-completely-compiled languages provide a way of caching compilation - through the use of pre-compiled libraries/programs/stuff ( lisp, python, java etc use such solutions )
Why doesn't perl pre-compile often-used things?
The way I see it, "Bytecode" support in perl is just a toy, and a way to show off the flexibility of the language.
What is missing is in-perl support for parse trees, something that would bypass whole compilation phase, and that would include libraries support.
This would have quite remarkable effect on perl
What bugs me, is the fact that when perl was being created, such pre-compiled bytecode support was en-vogue, lisp did it etc.. And since perl internally uses bytecode/parse tree, it would be trivial to add. What is the reason for that?