On Tue, Jul 29, 2003 at 11:17:27AM +0100, Edward Wildgoose wrote: > However, if you package up stuff with the activestate thing then the > perl script file is at least moderately well hidden, for example there > is only one useful reference on google on how to reverse engineer it, > and the method appears to be inapplicable for the latest version. (It > is certainly beyond anyone who is not at least extremely keen to look > inside)
Run a debugger. Break right after perl_parse. Dump the OP tree
and feed it to B::Deparse. I have verified this method's validity
with the author of PerlApp. :-)
> There are many hackers quite easily capable of reverse engineering
> this, and I have no intention of aiming at them, however, if one can
> prevent a customer opening it up in winzip then this is a step
> forward... (if you see what I mean)
Here we agree with each other. A plugin is planned during 0.7x as:
- Allow multiple (layered) ones via cmdline
- Takes either /path/to/command (piped to it) or
Foo::Bar::funcname (which automatically does a "require Foo::Bar")
Currently, I'm inclining to use "pp -F" / "pp --filter" for this
function. Suggestions welcome.
Thanks,
/Autrijus/
pgp00000.pgp
Description: PGP signature
