in reply to Re: obfuscating source code
in thread obfuscating source code

In fact, obfuscating code will prevent *you*, in the future, from being able to change that code.

Sure, you could obfuscate, give them the obfuscated version (which could always be deobfuscated) and make changes in your original version but once you'd do those changes you would have to obfuscate everything again to deliver it... that's not a good option :-|

Replies are listed 'Best First'.
Re^3: obfuscating source code
by diotalevi (Canon) on Dec 25, 2004 at 19:46 UTC
    I don't generally believe that because anyone going to obfuscate their source is more likely to use an automated method than doing it manually. Heck, you could even use my B::Deobfuscate module to do this. I meant to write a complementary obfuscating module but its quite a bit more of a pain since B::Deparse includes a lot of explanatory white space that's difficult to remove. The B::Deobfuscate module trivially renames things by subclassing B::Deparse and overriding some of the functions related to naming things.
[reply]

In Section Seekers of Perl Wisdom