]> git.ipfire.org Git - thirdparty/git.git/commit
check-non-portable-shell: improve `VAR=val shell-func` detection
authorEric Sunshine <sunshine@sunshineco.com>
Sat, 27 Jul 2024 05:35:09 +0000 (01:35 -0400)
committerJunio C Hamano <gitster@pobox.com>
Sat, 27 Jul 2024 05:49:40 +0000 (22:49 -0700)
commit7b9e54714a1c0b6f284cc7d8241e9ea25d149476
treed60c7b15b16d8ad7110f0e869ae11fffcb7d624d
parent7bd0cd0e7b29da382fcf2821c1bf087190ab2ffe
check-non-portable-shell: improve `VAR=val shell-func` detection

The behavior of a one-shot environment variable assignment of the form
"VAR=val cmd" is unspecified according to POSIX when "cmd" is a shell
function. Indeed the behavior differs between shell implementations and
even different versions of the same shell, thus should be avoided.

As such, check-non-portable-shell.pl warns when it detects such usage.
However, a limitation of the check is that it only detects such
invocations when variable assignment (i.e. `VAR=val`) is the first thing
on the line. Thus, it can easily be fooled by an invocation such as:

    echo X | VAR=val shell-func

Address this shortcoming by loosening the check so that the variable
assignment can be recognized even when not at the beginning of the line.

Signed-off-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
t/check-non-portable-shell.pl