good chemistry is complicated, and a little bit messy -LW |
|
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
I remember the link. I think it was Protecting Perl Code.
It was a slightly different issue -- this monk is
concerned about a particular thievery-prone person,
as opposed to the earlier monk who seemed to just be
generally paranoid.
I'm curious why SuperCruncher wants the other person to have a copy of the application at all -- is a face-to-face demo impossible or impractical? Stealing code against the author's wishes is SO gauche. Frankly, I'm not sure of what the best solution is. If the script is really big, I guess you'll have to compile it -- other people have actual technical suggestions on how to do this. Personally, I think it would be rather fun to go through the code and make it mostly-workable but wrong and bad and inefficient. Use . instead of join, s instead of tr, arrays instead of hashes. Put everything in one big object. Lowercase your filehandles and capitalize your subroutines. Indenting is a sign of brain fever. Use local when you mean my. (I could get carried away with this...) e-mail neshura In reply to RE: Re: Compiling Perl?
by neshura
|
|