Re: "unset var" pops var off variable stack instead of unsetting it
From:
Dan Douglas
Subject:
Re: "unset var" pops var off variable stack instead of unsetting it
Date:
Fri, 17 Mar 2017 21:38:55 -0500
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
On 03/17/2017 09:16 PM, Dan Douglas wrote:
> Why
> would a subshell just make the call stack go away?
I guess slight correction, it's unset itself, because:
> In fact, mksh prints "global" even without the subshell, despite it
> using dynamic scope for either function definition syntax.
Another "not-sure-if-bug-or-feature". It is a way to guarantee reaching
the global scope, which is impossible in bash, short of calling unset
${#FUNCNAME[@]} times.
If feature, I'm not instantly in love with it.