Re: Which shell and how to get started handling arguments

Kaz Kylheku <643-408-1753@kylheku.com> writes:

On 2024-04-16, Christian Weisgerber <naddy@mips.inka.de> wrote:

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.

>
"set -o posix" disabling conforming extensions would be a GCC-grade
stupidity.

An option to disable conforming extensions, whether it's spelled "set -o
posix" or in some other way, could be very useful for people who would
like to write scripts that don't (perhaps unintentionally) depend on any
extensions.

--
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 */