> Stuart> I have a few perl files that I need to send out to a > Stuart> client. However, we do not want them seeing what are in the > Stuart> files for obvious reason. > > What obvious reason?
That would be so the client doesn't walk away from the guys who do the work once they have the goods. > Stuart> Is there any way that I can hide the info in the files, or > Stuart> should I creat an executable. > > Please don't ask the very community that brought you Perl by making > Perl open source and all the contributions to Perl also open source, > to help you lock up something that you are making money with. Ah, you wish all the code in the world were viewable, me too. But it seems to me like a custom script for a client rather than something the whole world could use. At work, I would compile specific-task perl scripts for several reasons: 1) So my coworkers would not edit them and mess something up. 2) To make them wonder how I did it. 3) Because, if they could see the code they would tend to try to find some reason to criticize it (human nature). 4) For their ease of use, no perl.exe or perl56.dll required. 5) So that if they dump me and want an upgrade they have to start all over. ActiveState charges $200 and distributes exe's. Maybe they should stop doing that?? Stuart, install ActiveState and try PerlApp, it will function during the trial period. Or use Perl2Exe, your choice. /g -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
