I suggest that wrapping it in an executable should be considered a social measure. Its a clear sign that you don't want people to poke in there, although it won't stop them if they try.
In addition to appropriate contracts & licenses as above, you might also consider adding a watermark to the code to identify who leaked it when it inevitably gets out in a few years. Then bill the culprit for the extra copies floating around and/or damages incurred (write that part into the contract of course).
The only way to actually prevent the code from leaking is to keep it on trusted hardware being accessed only by trusted people ... even then, you can't be sure they're trustworthy or the only ones with access, but that is closer to a physical security issue. It also sounds like it isn't practical for your purpose.
In reply to Re: Automatically Converting Perl to C
by SuicideJunkie
in thread Automatically Converting Perl to C
by blueberryboost
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |