4 ms·
Okay. Care to point us all to the official standard POSIX flags documentation? Even then, you are probably going to find that there are just as many systems tha
by npsimons 14y ago
Okay. Care to point us all to the official standard POSIX flags documentation? Even then, you are probably going to find that there are just as many systems that your script needs to run on that are POSIX incompatible as there are systems that don't recognize the long flags.
My ultimate rule: write the code that is the most readable, because in 10, 15, 30 years, someone can easily update a script to working arguments from arguments with long words, whereas single letter arguments may have multiple different meanings on different systems. It's the same with naming conventions and code constructs: the how and the what should be obvious from the code.
- kps 14y agoFor documentation, this will do: http://pubs.opengroup.org/onlinepubs/009695399/utilities/contents.html http://pubs.opengroup.org/onlinepubs/009695399/utilities/con... What current systems have arguments that conflict with those?
- npsimons 14y agoFor documentation, this will do: http://pubs.opengroup.org/onlinepubs/009695399/utilities/con.. http://pubs.opengroup.org/onlinepubs/009695399/utilities/con.... Thank you for that. I was aware of the POSIX docs for C/system level programming, but I wasn't sure if command arguments were standardized. What current systems have arguments that conflict with those? Ah, but "current" is not always what we get. It's been a while, but I can vaguely remember conflicting single character arguments for basic commands (eg, ls, ps) on OSF/1, SunOS and Linux.