in reply to
Re: Re: Re: Here is a commercial obfuscator
in thread Here is a commercial obfuscator
Well... since the method name belongs to the LWP package I can't very well go changing that unless I perform the same steps on LWP as well. Anyhow, the patch as written renames pad and stash accesses. It does introduce bugs where otherwise correct accesses to %ENV would now fail. If the obfuscator were actually correct it'd need to have special cases to avoid changing things that shouldn't be. I figure that's best implemented by adding support for a list of expressions that may not be altered. Anyhow, since I don't need an obfuscation filter I'm not going to alter B::Obfuscate to add that support. Changing string constants is somewhat problematic but not irresolvable given the framework provided by B::Deparse.
I'll leave it to someone else to extend the new module.
Seeking Green geeks in Minnesota