You don't need a command line switch unless<br>you want to pass args:<br><br>% echo 'print "hi\n";' | perl <br>hi<br>% echo 'print "@ARGV\n";' | perl - a1 a2<br>a1 a2<br><br>JD<br><br><div><span class="gmail_quote">
On 9/7/06, <b class="gmail_sendername">David S. Patterson</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'm trying to kludge together a strategy to protect some perl source code from<br>prying eyes (this would be on a Unix-like system).<br><br>I'm thinking of a solution in which a simple compiled front-end program reads<br>
an encrypted text file, decodes it internally into a perl script, and then<br>execs or launches the perl executable and somehow provides the decoded perl<br>script to it. The point is that the decoded perl script must never become a
<br>temporary file that a "casual user" could edit. I think that temporary pipe<br>files would be fine, finding and opening those is not "easy".<br><br>Does anyone have any ideas or suggestions about this?
<br><br>Is it possible to "pipe" a file to perl and have it execute it? Can it be<br>done with the right command line switch?<br><br>e.g.: $ cat foo.pl | perl<br><br>Thanx,<br><br>-Pat<br><br><br>_____________________________________________________________
<br>Seattle Perl Users Group Mailing List<br> POST TO: <a href="mailto:firstname.lastname@example.org">email@example.com</a><br>SUBSCRIPTION: <a href="http://mail.pm.org/mailman/listinfo/spug-list">http://mail.pm.org/mailman/listinfo/spug-list
</a><br> MEETINGS: 3rd Tuesdays<br> WEB PAGE: <a href="http://seattleperl.org/">http://seattleperl.org/</a><br></blockquote></div><br>