[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: -ash: changed behaviour of local vars / v1.22.1 -> v1.23.2
From:       Denys Vlasenko <vda.linux () googlemail ! com>
Date:       2015-04-18 17:39:06
Message-ID: CAK1hOcNYXQKjWKiLJeGse+BfiowV2AuzBmSocnQMoFYx+WG==g () mail ! gmail ! com
[Download RAW message or body]

Fixed in git.

On Fri, Apr 17, 2015 at 12:53 PM, Cristian Ionescu-Idbohrn
<cristian.ionescu-idbohrn@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
>> example (tested with bash 4.1 & 4.3). I believe if the variable should
>> be unset should depend on its (variables) scope.
>
> Even if "bash does that", it isn't necessary the right thing to do. I
> have lots of scripts relying on former behaviour (inherit initial
> local variable value from the calling scope).  The current behaviour
> is a regression, AFAICT.  `dash' does not behave like `bash' either.
>
> I guess I'll have to carry a local patch reverting that commit :(
>
>
> Cheers,
>
> --
> Cristian
> _______________________________________________
> busybox mailing list
> busybox@busybox.net
> http://lists.busybox.net/mailman/listinfo/busybox
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]