On Fri, Feb 15, 2013 at 8:19 PM, Rajeev Prasad <rp.ne...@yahoo.com> wrote: > it not only decreases the size, to load in RAM, also make it 'little harder' > for cocky-novices to steal the tricks (perl guru's anyway dont care). > > > http://www.stunnix.com/prod/po/ (binary not present to download??) > http://blueboxtech.co.uk/perlplexity/ (failed to remove trailing comments...) > http://creativyst.com/cgi-bin/Prod/19/eg/PerlPack.pl
Actually, it would probably use more RAM when compressed, so if that's your aim, this is the most counterproductive approach*; and in any case, the resulting optree would be of the same size regardless of the original code size. More importantly, no matter what solution you intend to use, if the code ultimately needs to be fed to perl, it doesn't stop anyone from calling it with -O=Deparse and getting a sane version; or if they have the "compressed" source, from just running it through perltidy. Trying to hide the source is a pointless, losing battle. That being said, you could try using B::C or PAR/FatPacker (I forget which) to distribute a binary of your program, which I imagine would be harder to read into. * perl reads the source line-by-line, only grabbing several lines at once when it needs to, like in multiline expressions or heredocs. A compressed program would put even more characters in a single line, forcing perl to use a bigger buffer, thus more RAM. -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
