Re: Which shell and how to get started handling arguments

Christian Weisgerber <naddy@mips.inka.de> writes:

On 2024-04-15, Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:

Bash has an option that tells it to (attempt to) restrict itself to
POSIX semantics:

>
No, it does not:
>

    Starting Bash with the '--posix' command-line option or executing
    'set -o posix' while Bash is running will cause Bash to conform more
    closely to the POSIX standard by changing the behavior to match that
    specified by POSIX in areas where the Bash default differs.

                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
This only tweaks bash's behavior where it otherwise differs from
POSIX.  It does not disable the myriad extensions.

I stand corrected.

There is a tool ShellCheck that among other things can be used to
warn about unportable code in shell scripts.
https://www.shellcheck.net/
>
I haven't used it myself yet.  It is written in Haskell, so it
suffers itself from portability concerns.

There's also a "shellcheck" application, installable as a package on
Ubuntu and presumably many other systems.  I use it regularly, almost
always on scripts with "#!/bin/bash" so it doesn't check POSIX rules.
But when invoked on a script with "#!/bin/sh" or with "--shell=sh" it
claims to warn about POSIX portability issues.

https://github.com/koalaman/shellcheck

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Medtronic
void Void(void) { Void(); } /* The recursive call of the void */