Path: csiph.com!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: =?utf-8?Q?Lawrence_Vel=C3=A1zquez?= <vq@larryv.me>
Newsgroups: gnu.bash.bug
Subject: Re: set -u not working as expected
Date: Sat, 1 Aug 2020 20:47:42 -0400
Lines: 68
Approved: bug-bash@gnu.org
Message-ID: <mailman.473.1596329270.2739.bug-bash@gnu.org>
References: <000301d66834$588493c0$098dbb40$@kalvr.net> <F4821044-5F8D-4B6D-A266-BAC88AE3DC2C@larryv.me>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.15\))
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: bug-bash@gnu.org
To: Kristof Burek <contact@kalvr.net>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <000301d66834$588493c0$098dbb40$@kalvr.net>
Received-SPF: pass client-ip=64.147.123.21; envelope-from=vq@larryv.me; helo=wout5-smtp.messagingengine.com
X-Spam_score_int: -27
X-Spam_score: -2.8
X-Spam_bar: --
X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-BeenThere: bug-bash@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-bash>
List-Post: <mailto:bug-bash@gnu.org>
List-Help: <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID: <F4821044-5F8D-4B6D-A266-BAC88AE3DC2C@larryv.me>
X-Mailman-Original-References: <000301d66834$588493c0$098dbb40$@kalvr.net>
Xref: csiph.com gnu.bash.bug:16671

> On Aug 1, 2020, at 2:48 PM, Kristof Burek <contact@kalvr.net> wrote:
>=20
> set -u  # Bash complains and exits on first use of an unbound name

With respect to set -u neither the bash man page nor POSIX.1-2017
refer to "use" of parameters, but to their *expansion*.

> s+=3D't' # Line 8 - Bash should fail here

I don't see any parameter expansion here, and ksh and zsh agree:

% bash --version | head -n 1; ksh --version; zsh --version
GNU bash, version 5.0.17(1)-release (x86_64-apple-darwin18.7.0)
  version         sh (AT&T Research) 93u+ 2012-08-01
zsh 5.8 (x86_64-apple-darwin18.7.0)
% bash -c 'set -u; unset s; s+=3Dt; printf "<%s>\\n" "$s"'
<t>
% ksh -c 'set -u; unset s; s+=3Dt; printf "<%s>\\n" "$s"'
<t>
% zsh -c 'set -u; unset s; s+=3Dt; printf "<%s>\\n" "$s"'
<t>

Presumably none of these shells implements s+=3Dt as s=3D${s}t.

> #t=3D''
> t=3D${t}'t' # Line 12, Bash fails until line 11 loses its starting #

This fails as you expect because you're expanding $t in there.

> u+=3D('t') # Line 15, Bash should fail here

Again, I don't see any parameter expansion here, and ksh and zsh
agree:

% bash -c 'set -u; unset u; u+=3D(t); printf "<%s>\\n" "${u[@]}"'=20
<t>
% ksh -c 'set -u; unset u; u+=3D(t); printf "<%s>\\n" "${u[@]}"'=20
<t>
% zsh -c 'set -u; unset u; u+=3D(t); printf "<%s>\\n" "${u[@]}"'=20
<t>

Presumably none of these shells implements u+=3D(t) as u=3D("${u[@]}" =
t).

> let v+=3D1 # Line 18, Once line 11 is uncommented, Bash fails here

I haven't seen the code for arithmetic expansion, but I assume it
treats v+=3D1 as morally equivalent to v=3D${v}+1 (=C3=A0 la C99). Thus =
there
*is* an expansion, which fails under set -u. Regardless of the
particulars, ksh and zsh again agree:

% bash -c 'set -u; unset v; let v+=3D1; printf "<%s>\\n" "$v"'
bash: v: unbound variable
% ksh -c 'set -u; unset v; let v+=3D1; printf "<%s>\\n" "$v"'
ksh: let: v: parameter not set
ksh: v: parameter not set
% zsh -c 'set -u; unset v; let v+=3D1; printf "<%s>\\n" "$v"'
zsh:1: v: parameter not set
zsh:1: v: parameter not set

> When this issue is fixed, I dare say a few perfectly working scripts
> will fall over, but I hope not too many of mine.

It's not clear that there's a bug here.

vq=