declare in a function makes a variable unable to be found with declare -p in some cases

2015-02-16 Thread SN
Hello all, I have found a problem with the declare builtin. Patch Level: 33 Release Status: release Description: Apparently, there is a problem with how bash interprets some variable assignments. It only happens in a function (probably related to `declare' making variables local)

Re: declare in a function makes a variable unable to be found with declare -p in some cases

2015-02-17 Thread SN
> Already reported: > > * test -v: http://lists.gnu.org/archive/html/bug-bash/2014-11/msg00099.html > * declare -p arrname: > https://lists.gnu.org/archive/html/bug-bash/2012-11/msg00084.html The second thread is about something completely different as I understand it. It is about variables whose

Re: declare in a function makes a variable unable to be found with declare -p in some cases

2015-02-18 Thread SN
> Also, remember to state the version you're using. I pasted version in the format printed by bashbug. In case it's not enough: $ LANG=C bash --version GNU bash, version 4.3.33(1)-release (x86_64-pc-linux-gnu) ... > This particular > feature seems to behave differently in the -devel branch: > > >

Re: declare in a function makes a variable unable to be found with declare -p in some cases

2015-02-20 Thread SN
> Yes. The issue is that the assignment doesn't make the variable visible, > when it clearly should. I've attached a patch that will fix that. And it does. > The next version of bash will do things differently, as noted in a couple of followups to this message. The proposal that prompted the cha