Re: I am not now, nor have I ever been, a Perl compiler...

[Steffen Mueller]

John Adams wrote:
[...]

Short answer: In a lot of cases, you get enough performance advantage
by writing an XS extension or using the Inline module to put the
heavy lifting into C (or some other language, for that matter) and
pasting it into Perl.

Actually, you get much *more* performance that way than what you'd get if you used perlcc (don't!) or even perlapp, etc. to compile / package your scripts.

You might also look into the perl2exe tool from ActiveState--I'm not
sure what it costs.

Erm, isn't that perlapp from AS and perl2exe from indigo or something like that?

So--how's this answer? I have already noticed that the FAQs at
perl.com are 5.6 FAQs--anything else?

I think the FAQs explain quite a lot about the problem of compiling Perl vs. packaging it using perlapp or perl2exe. The solution is: Don't. If you want performance, get it elsewhere. If you want security by obscurity, well, find another job (and get it elsewhere). If you just want to distribute stand-alone executables, then go for perlapp or perl2exe. Just don't expect them to speed up your code or make it unreadable.

Steffen
--
sub'_{q} tsuJ}}_();sub's{seek+DATA,0,0}sub'p{print&_}sub'r{reverse$_[0]}
@_=(('')x2,split" ",<DATA>);s!!&s,$_=<DATA>;s/}.*?}/$_[$s+1]/
if$s;s/(}.*?})/r$1/e;eval$_;p,$s++!efor@_[0..3];
__DATA__
} rehtona} } lreP} },rekcah}