Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Chet Ramey <chet.ramey@case.edu>
Newsgroups: gnu.bash.bug
Subject: Re: Expansions based on variable existence (e.g. ${var+exists}) yield inconsistent results.
Date: Mon, 20 Apr 2020 15:38:02 -0400
Organization: ITS, Case Western Reserve University
Lines: 89
Approved: bug-bash@gnu.org
Message-ID: <mailman.823.1587411492.3066.bug-bash@gnu.org>
References: <courier.000000005E9DC602.00021742@charon.podzimek.org> <63c348fe-0db3-b419-b544-3a67b6aa1472@case.edu>
Reply-To: chet.ramey@case.edu
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Cc: chet.ramey@case.edu
To: andrej@podzimek.org, bug-bash@gnu.org
Envelope-to: bug-bash@gnu.org
Autocrypt: addr=chet.ramey@case.edu; prefer-encrypt=mutual; keydata= mQGiBEEOsGwRBACFa0A1oa71HSZLWxAx0svXzhOZNQZOzqHmSuGOG92jIpQpr8DpvgRh40Yp AwdcXb8QG1J5yGAKeevNE1zCFaA725vGSdHUyypHouV0xoWwukYO6qlyyX+2BZU+okBUqoWQ koWxiYaCSfzB2Ln7pmdys1fJhcgBKf3VjWCjd2XJTwCgoFJOwyBFJdugjfwjSoRSwDOIMf0D /iQKqlWhIO1LGpMrGX0il0/x4zj0NAcSwAk7LaPZbN4UPjn5pqGEHBlf1+xDDQCkAoZ/VqES GZragl4VqJfxBr29Ag0UDvNbUbXoxQsARdero1M8GiAIRc50hj7HXFoERwenbNDJL86GPLAQ OTGOCa4W2o29nFfFjQrsrrYHzVtyA/9oyKvTeEMJ7NA3VJdWcmn7gOu0FxEmSNhSoV1T4vP2 1Wf7f5niCCRKQLNyUy0wEApQi4tSysdz+AbgAc0b/bHYVzIf2uO2lIEZQNNt+3g2bmXgloWm W5fsm/di50Gm1l1Na63d3RZ00SeFQos6WEwLUHEB0yp6KXluXLLIZitEJLQwQ2hldCBSYW1l eSAoQ2FzZSBzdGFuZGFyZCkgPGNoZXQucmFtZXlAY2FzZS5lZHU+iF8EExECAB8FAkPi19EC GwMHCwkIBwMCAQMVAgMDFgIBAh4BAheAAAoJELtYafBk6nSrelkAn31Gsuib7GcCZHbv5L5t VKYR9LklAJ4hzUHKA49Z0QXR+qCb80osIcmPSbkBDQRBDrBvEAQAkK6TAOKBEM+EC4j6V/7o /riVZqcgU5cid2qG9TXdwNtD9a3kvA/ObZBO93sX59wc6Bnwo4VJxsOmMlpGrAjJsxNwg3QH akEtf8LXRbVpj5xStdmBdQZUhIQyalo/2/TZq5OijtddUQcL5cs70hTv/FpT3wUvr2Xr8rjF 41IFEz8AAwcD/A0CZEGlzIrT5WCBnl6xBog/8vKiUCbarByat3d1mL6DbizvKNXQRTC9E/vE dENAWCQCjr75Bu55xT8n3SXGtWdDC5xmZ/P3OBYORP8yl8H8I1FIosWOFirbIeYdZPq8SPD1 HL+EXo9zSiHVrrZRJ19ooCKKbSdXHFCY+aJG+0KZiEkEGBECAAkFAkEOsG8CGwwACgkQu1hp 8GTqdKvjcACfZlkVCDwaz/NTO9cy3t69oWpVPNwAnRwe0qk/WL/gfhH346xh5B3HFbFN
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.7.0
In-Reply-To: <courier.000000005E9DC602.00021742@charon.podzimek.org>
Content-Language: en-US
Received-SPF: pass client-ip=129.22.103.194; envelope-from=chet.ramey@case.edu; helo=mpv3-2015.case.edu
Precedence: list
Xref: csiph.com gnu.bash.bug:16195

On 4/20/20 11:55 AM, andrej--- via Bug reports for the GNU Bourne Again
SHell wrote:

> Bash Version: 5.0
> Patch Level: 16
> Release Status: release
> 
> Description:
>   Variable existence testing doesn't match variables that are (only) declared.
>   Unless the declared variables are redeclared as arrays. Other variable
>   existence tests yield surprising results as well. (This is all about existence
>   tests, i.e., ones without the extra ':' that tests for emptiness.)
> 
>   In particular, Example 4 below exposes a situation in which a variable doesn't
>   seem to be set, yet cannot be set. Example 5 below shows that empty arrays
>   are treated differently in terms of variable existence. Also, redeclaration of
>   a variable as an array seems to have an "assignment effect" on it (in the
>   sense of making it detectable by existence tests). Redeclaration as an integer
>   doesn't have this effect.
> 
> Repeat-By:
>   Example 1:
>   declare var                   # The same problem occurs with -i, -a and -A.
>   echo "${!var@}"               # empty [unexpected]
>   echo "${var+exists}"          # empty [unexpected]
>   echo "${var-nonexistent}"     # nonexistent [unexpected]

var is unset; you have not assigned a value.

> 
>   Example 2:
>   declare var
>   declare -A var

This is a bug; var should remain unset since it has no value. It happens as
part of the process converting the variable to an associative array.

>   echo "${!var@}"               # var [expected] << Difference from Experiment 1
>   echo "${var+exists}"          # empty [unexpected]
>   echo "${var[@]+exists}"       # empty [somewhat unexpected]
>   echo "${var-nonexistent}"     # nonexistent [unexpected]
>   echo "${var[@]-nonexistent}"  # nonexistent [somewhat unexpected]


> 
>   Example 3:
>   declare var=
>   echo "${!var@}"               # var [expected]
>   echo "${var+exists}"          # exists [expected]
>   echo "${var-nonexistent}"     # empty [expected]

var is set with an empty value.

> 
>   Example 4:
>   declare -r var
>   echo "${!var@}"               # empty [unexpected]
>   echo "${var+exists}"          # empty [unexpected]
>   echo "${var-nonexistent}"     # nonexistent [unexpected]
>   var=                          # Error! [inconsistent]

var is unset until you attempt to assign it a value. It exists only as an
unset variable with attributes.

> 
>   Example 5:
>   var=()
>   echo "${!var@}"               # var [expected]
>   echo "${var+exists}"          # empty [unexpected]
>   echo "${var[@]+exists}"       # empty [somewhat unexpected]

An empty array is set (or, more precisely, it is not unset). It's like
assigning a null string to a variable.

>   echo "${var-nonexistent}"     # nonexistent [unexpected]

This is the same as var[0].

>   echo "${var[@]-nonexistent}"  # nonexistent [somewhat unexpected]

There aren't any values there. I suppose it could expand to the empty
string, but it doesn't.


-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/