Re: Unset array doesn't work

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: Unset array doesn't work
Date	2018-02-28 15:14 -0500
Message-ID	<mailman.9903.1519848908.27995.bug-bash@gnu.org> (permalink)
References	(5 earlier) <755d61fa-d2bc-8855-bc30-4388aff40691@gmail.com> <9974.1519637469@jinx.noi.kre.to> <15717.1519764581@jinx.noi.kre.to> <24248.1519844400@jinx.noi.kre.to> <20180228200051.ilzre3k4y7intd76@eeg.ccf.org>

Show all headers | View raw

On 2/28/18 3:00 PM, Greg Wooledge wrote:

> Does unset create some kind of "placeholder" in the current function
> (but not in a caller)?

Yes, that's what I said. In the current scope, unset arranges for the
variable to appear unset. In a previous scope, unset just removes the
variable, which uncovers an instance of the variable at a (further)
previous scope.

It looks like I added that code in 1995. The code before that was "pure"
dynamic scoping, in the sense that it just removed the variable and
`uncovered' a previous scope's value no matter where the variable was
declared. It seems like I added the special case for several reasons,
but there's no indication of widespread user complaint about the behavior
of `unset'. (Of course, that was a long time ago.)

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: Unset array doesn't work Chet Ramey <chet.ramey@case.edu> - 2018-02-28 15:14 -0500

csiph-web