I think so.
The bourne shell itself already has so many variants that I would not bet on anything more complex than '/path/to/program' 'arg1' 'arg2' ... 'argN' to work reliably across all those shells, and even that only for small values of N, and not for the entire charset. Especially not on systems from the last century.
Even "$@" has two implementation variants that can cause trouble, leading to the cryptic ${1+"$@"} in perlrun.
There are Portability Notes for shell programming, lots of them.
Things get worse outside the Unix world, especially with Microsoft systems (DOS, Windows, OS/2). I learned from experience that it is often easier to get out of the shell as fast as possible and let perl do the job without any support from the shell beyond passing parameters to perl.
Alexander
--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.