comment on

For casual scripts, I've always used the following:

eval '(exit $?0)' && eval 'exec perl -w -S $0 ${1+"$@"}'
                  && eval 'exec perl -w -S $0 $argv:q'
                  if 0;

# The above invocation finds perl in the path, wherever it may be
[download]

(I've forgotten where I stole this from.)

Is there a "best" way to get whichever perl is in your path?

I hadn't seen the env version before, nice.

I also agree, in many cases the shebang line should point to a fixed Perl. I can even see an argument for not giving any shebang hints, and always invoking the perl binary explicitly from an external source.

-QM
--
Quantum Mechanics: The dreams stuff is made of

In reply to Re: #!/usr/bin/perl vs. -*- perl -*- by QM
in thread #!/usr/bin/perl vs. -*- perl -*- by why_bird

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Clear questions and runnable code get the best and fastest answer
	PerlMonks