note
Bloodnok
Further to the excellent response from [Tux], I tend to use the form <c>#!/usr/bin/env perl</c> which <i>pulls</i> the version of perl from your environment - this is handier if, as I have, you one, or other, or both, of the following situations...
<ul>
<li> Different versions of perl against which you are(required to be) testing/running your code &/or...
<li> Different *NIX platform configurations on which you are testing/running your code
</ul>
<p>
The above is, of course, moot if you have to run on Windoze, where all sorts of other problems come into play e.g. as you suggest, the shebang line is ignored etc. hence work-rounds have to be used e.g. batch files containing the full perl script (incl. the shebang line) together with the <c>-x</c> CLI option (see [perldoc://perlrun]).
<p>
<div class="pmsig"><div class="pmsig-264639">
A user level that continues to overstate my experience :-))
</div></div>
737548
737553