| [reply] |
One well-known (though not always well liked) approach to this in the Enterprise market is to protect the code with NDAs and license agreements with confidentially and though-shalt-not-peek clauses. It doesn't really prevent anyone from seeing your source code, but it may give them second thoughts about doing anything untowards with it.
| [reply] |
There is one way that I could think of to do this: Distribute a binary version, using a program like perl2exe
- p u n k k i d
"Reality is merely an illusion,
albeit a very persistent one."
-Albert Einstein | [reply] |
What about Bleach from CPAN? It might offer you a little protection. It converts your code into whitespace which actually contains the encoded source. If you then keep the use line in, the module will decode the source and run it when the program is run. I didn't think my program would run after I Bleached it, until it ran, correctly... but when I viewed it in the editor it was all white...
...of course someone intent at getting at the source could still modify Bleach to allow them to view it, but you can protect your source from that with a restrictive license (as others have suggested). | [reply] |