Some notes below your chosen depth have not been shown here 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?īy perlboy_emeritus (Sexton) on at 15:27 UTC 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. However, unless I am doing something wrong, it does not work for me. (the same as you might get on other systems if you tried /usr/bin/env 'perl -w' or /usr/bin/env 'perl\ -w'.)Īpart from all the examples given, there is a script in that page called "cmd" which allegedly will solve your problem by using: Because it's one entity, then some versions of env will try to run "perl -w", and doesn't find anything to run that's P E R L SPACE DASH W as the name. The "/usr/bin/env" is the interpreter, and "perl -w" or "perl -wd" is the single parameter (argument). I don't know if you ever gathered this from the other replies, but from choroba's "interpreter and parameter" and your "in both of those example shebangs, I cannot have any arguments" shows that, at least originally, you didn't understand. is pretty widespread, so you simply cannot rely on being able to pass more than one argument.
After all, in most operating systems, whitespace or dashes are legal in a path.Ģ Some operating systems split at whitespace and treat the first part as the path to the interpreter and the rest as individual arguments.ģ Some operating systems split at the first whitespace and treat the front part as the path to the interpeter and the rest as a single argument (which is what you are seeing).Ĥ Some even don't support shebang lines at all. There is no consensus about what happens if it contains whitespace.ġ Some operating systems simply treat the entire thing as the path.
#Shebang for bash on mac full#
The assumption is that everything between the ! and the \n is a full absolute path to the interpreter. There is a rough consensus about what it does: take everything between the ! and the \n and exec it. AFAIK, it hasn't even been properly documented. The shebang line has never been specified as part of POSIX, SUS, LSB or any other specification. In both of those example shebangs, I cannot have any arguments no matter how I quote them, and I've tried every quote option there is. True, if the argument was an argument list I would certainly quote it so that it appears as a single argument. That page says the command can take an argument. In debian I cannot have any argument to perl from an /usr/bin/env shebang despite rtfm. Both these shebang lines fail in debian but work correctly in macOS. When I wish to debug I invert the lines, comment out the second, uncomment the first and proceed. I switch between these two lines, the first for ordinary runs, the second for debug runs.
0 kommentar(er)
