Re: Unset array doesn't work

From	Robert Elz <kre@munnari.OZ.AU>
Newsgroups	gnu.bash.bug
Subject	Re: Unset array doesn't work
Date	2018-03-01 05:38 +0700
Message-ID	<mailman.9914.1519857591.27995.bug-bash@gnu.org> (permalink)
References	(6 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

    Date:        Wed, 28 Feb 2018 15:14:58 -0500
    From:        Chet Ramey <chet.ramey@case.edu>
    Message-ID:  <b4615d2e-cf2f-ea60-c8c6-44b6eb8dba76@case.edu>

  | 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.

Were I you, I would simply change the "in a previous scope" behaviour to
match the "in the current scope" behaviour.   That makes it consistent,
and rational.

I cannot believe that there is anything anywhere which depends upon the
current weirdness.

I'd also forget "remove" as anything that unset is supposed to achieve,
and I would change "appear" to "be" in the description of the current scope
behaviour.

kre

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

Thread

Re: Unset array doesn't work Robert Elz <kre@munnari.OZ.AU> - 2018-03-01 05:38 +0700

csiph-web