in reply to Re: Perl 5 Optimizing Compiler, Part 2
in thread Perl 5 Optimizing Compiler, Part 2

This guarantees that each release of Perl requires a re-compile of all scripts or just keep all scripts as source-code.

... only in as much as every C program needs to be recompiled whenever a new version of gcc is released.

I would assume that a compiled Perl program includes all its constituents (modulo external, non-XS dynamic libraries), and thus is basically a stand-alone executable.

But then again, I don't care much for either side of this argument, as for me the interpreter has been fast enough in the parts where I use it.

Replies are listed 'Best First'.
Re^3: Perl 5 Optimizing Compiler, Part 2
by flexvault (Monsignor) on Aug 18, 2012 at 14:10 UTC

    Hello Corion,

    I think you're confusing my portability and scalability issues with others requirements for speed and/or obfuscation. I have stated on PM that 'Perl just gets better and better" and I meant it. I don't have issues with Perl's speed.

    Also I do have programs that were compiled in 1990 on pre-released IBM RS/6000 computers running AIX 3.0 beta ( AIX 3.1.5 was the official release in 1991 ) that can run today on 'power 7, p-series computers running AIX 7.1'. The computers are binary compatible even though the source code doesn't compile. K&R 'C' is considered traditional today, and most 'C' products no longer support traditional code.

    IMHO, if you ever have to authorize a '10 man-year' project to manually update source code on 2500+ computers, instead of remotely updated the compiled code over a weekend, then maybe you would see it as a little bigger and different problem.

    Thank you

    "Well done is better than well said." - Benjamin Franklin

[reply]

In Section Seekers of Perl Wisdom