Fixed in git.
On Fri, Apr 17, 2015 at 12:53 PM, Cristian Ionescu-Idbohrn
cristian.ionescu-idbo...@axis.com wrote:
On Thu, 16 Apr 2015, Eugene Rudoy wrote:
@Denys: your commit-message states bash does that. bash indeed does
so for the test-case from your commit, but doesn't do so for Bastians
* Eugene Rudoy gene.de...@gmail.com [17.04.2015 08:13]:
@Bastian: see 109ee5d336, your example is however quite strange -
what's the reason for declaring the variable twice, what's the real
use-case?
in fact it's a mistake in my script - but it has totally
changed the logic of my function, so
On Thu, 16 Apr 2015, Eugene Rudoy wrote:
@Denys: your commit-message states bash does that. bash indeed does
so for the test-case from your commit, but doesn't do so for Bastians
example (tested with bash 4.1 4.3). I believe if the variable should
be unset should depend on its (variables)
Hi,
@Bastian: see 109ee5d336, your example is however quite strange -
what's the reason for declaring the variable twice, what's the real
use-case?
@Denys: your commit-message states bash does that. bash indeed does
so for the test-case from your commit, but doesn't do so for Bastians
example
while heavy testing of recent OpenWrt i
discovered the following problem:
x() { local x=1; echo $x; local x; echo $x; }
older busybox will output
1
1
and v1.23.2 will only output
1
this means: 'local varname' will empty the var.
is this a problem with a changed config? at least
i cannot find a
