Our current method to run perl, is a wrapper script which determines what machine you are on, and finaly calls the correct PERL executable. The script begins with #!/usr/bin/sh. Now my personal perl script begins with: #!/usr/bin/env /bin/perl_wrapper -w this problem is a Unix problem where the -w is interpreted as a file name, and I get a -w file not found error. If I remove the -w, the nested scripts work fine. Is there another method to have the first line of my personal PERL script call a wrapper (for binary selection) and still pass perl options. Or a bteer way to select the right binary? Users may want specific perl versions. Thanks, Dan
#!/usr/bin/env perl_wrap -w #Above line fails with -w not found #!/usr/bin/env perl_wrap #Above line works fine
In reply to How can I control perl binaries by Dan.Pinvidic
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |