Re: /usr/bin/env - Incorrect parsing of #! line? Something that works!

nd of syntax the running shell accepts (Bourne shell style or C shell style) and then calls perl in a way appropriate for the running shell. eval '(exit $?0)' && eval 'exec perl -wS $0 ${1+"$@"}' & eval 'exec perl -wS $0 $argv:

Re: /usr/bin/env - Incorrect parsing of #! line?

Secondly, I run Perl with many different combinations of options, like "perl -w", "perl -wn", "perl -0777 -wn", etc. which makes that approach even far less feasible. By the way, you did mean "$@" and not $*, didn't you? :-) Peter -- Peter J. Acklam

Re: /usr/bin/env - Incorrect parsing of #! line?

[EMAIL PROTECTED] (William F. Hammond) writes: > I don't understand why you want to use /usr/bin/env > under Cygwin. The reason is portability. I have written hundreds of Perl utilities which I find extremely useful and I want them to run smoothly both on UNIX and cygwin. I really hesitate to m