Hi
See perlrun , when #!/usr/bin/env perl -l doesn't work use #!/bin/sh
#! -*-perl-*-
eval 'exec perl -x -wS $0 ${1+"$@"}'
if 0;
Also see https://www.in-ulm.de/~mascheck/various/shebang/#splitting which says Splitting arguments
A very few systems deliver only the first argument, some systems split
+ up the arguments like a shell to fill up argv[],
most systems deliver all arguments as a single string. See the table b
+elow. I noticed that for Linux (delivering all arguments as one strin
+g),
a patch to split up was suggested on the Linux kernel mailing list (de
+ad link, try this page, archive.org), followed by a discussion of som
+e portability issues.
See also https://unix.stackexchange.com/questions/361794/why-am-i-able-to-pass-arguments-to-usr-bin-env-in-this-case?rq=1, https://stackoverflow.com/questions/4303128/how-to-use-multiple-arguments-for-awk-with-a-shebang-i-e...
-
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.
|