in reply to Re^2: shebang anomaly
in thread shebang anomaly
Apart from all the examples given, there is a script in that page called "cmd" which allegedly will solve your problem by using: #!cmd /usr/bin/env perl -w. However, unless I am doing something wrong, it does not work for me. Although it should because what it does is straight-forward: breaks the command line and spawns yet another perl process with these args and your actual perl script.
Maybe you will have better luck than me if you were to try having two shell scripts perlw.sh and perlwd.sh calling perl differently?
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^4: shebang anomaly
by perlboy_emeritus (Scribe) on Apr 20, 2018 at 15:27 UTC | |
by Anonymous Monk on Apr 20, 2018 at 16:51 UTC | |
by perlboy_emeritus (Scribe) on Apr 20, 2018 at 20:33 UTC | |
by huck (Prior) on Apr 20, 2018 at 22:19 UTC | |
by jeffenstein (Hermit) on Apr 23, 2018 at 15:00 UTC | |
| |
| |
by bliako (Monsignor) on Apr 20, 2018 at 18:51 UTC |
In Section
Seekers of Perl Wisdom