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-03-02 14:49 -0500
Message-ID	<mailman.10033.1520020196.27995.bug-bash@gnu.org> (permalink)
References	(7 earlier) <9974.1519637469@jinx.noi.kre.to> <15717.1519764581@jinx.noi.kre.to> <24248.1519844400@jinx.noi.kre.to> <20180228200051.ilzre3k4y7intd76@eeg.ccf.org> <18844.1519857511@jinx.noi.kre.to>

Show all headers | View raw

On 2/28/18 5:38 PM, Robert Elz wrote:

> I would change "appear" to "be" in the description of the current scope
> behaviour.

Now we're straying into semantics. If the variable were `really' unset,
as opposed to just appearing unset, that could be construed as meaning
the global instance (or any previous local instances) would be gone, too.
I could see pairing it with text that says the variable at the current or
nearest previous instance is unset and remains so until that function
returns.

Chet
-- 
``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-03-02 14:49 -0500

csiph-web