in reply to Automatically Converting Perl to C

Rather than coming up with a programming solution to protecting your work by making it a little harder to read, is it possible to achieve one of the following?

My point is that creating an executable with the intent of simply making it more difficult to read what you've written (first) won't guarantee that you'll accomplish the goal, and (second) may not be the most effective approach. There may be better ways to protect your interests. Think a little outside the technical box and you may come up with a real-world solution that is more appropriate.


Dave

Replies are listed 'Best First'.
Re^2: Automatically Converting Perl to C
by blueberryboost (Novice) on Apr 02, 2010 at 16:07 UTC
    Dave, Thanks for your suggestions. Unfortunately in the particular niche I am working I need more protection than the "non-technical solutions" you have kindly listed. Also, the constraint that I have right now is that an executable needs to leave my hands, I cannot at this point keep the exec on my machine ans allow remote access through an API...