On 11/27/16 5:07 AM, Otenba wrote:
> Bash Version: 4.4
> Patch Level: 5
> Release Status: release
>
> Description:
> Performing variable indirection using an empty value causes an error. It
> didn't in Bash 4.3.
It's pretty clear that indirect expansion that attempts to reference
through an unse
On Mon, Nov 28, 2016 at 5:03 PM, Otenba wrote:
>>It is indeed an error to attempt to perform indirection on an empty or
>> unset parameter.
> What I showed was that it is an error only for an empty parameter. If it's
> unset then it will do what it did in Bash 4.3, which is return an empty
> strin
>It is indeed an error to attempt to perform indirection on an empty or unset
>parameter.
What I showed was that it is an error only for an empty parameter. If it's
unset then it will do what it did in Bash 4.3, which is return an empty string
without error.
And another possibility is if the in
This change of behavior is the result of a bug fix for
http://lists.gnu.org/archive/html/bug-bash/2015-08/msg00058.html,
introduced in the following commit
http://git.savannah.gnu.org/cgit/bash.git/commit/?id=f2d7e1a3bcbdec7ef09db71779d800237fbc58bb
(read the changelog in CWRU/CWRU.chlog)
A couple
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu'
-DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash'
-DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./
