Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #13779 > unrolled thread
| Started by | Robert Elz <kre@munnari.OZ.AU> |
|---|---|
| First post | 2018-03-01 05:38 +0700 |
| Last post | 2018-03-01 05:38 +0700 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Unset array doesn't work Robert Elz <kre@munnari.OZ.AU> - 2018-03-01 05:38 +0700
| From | Robert Elz <kre@munnari.OZ.AU> |
|---|---|
| Date | 2018-03-01 05:38 +0700 |
| Subject | Re: Unset array doesn't work |
| Message-ID | <mailman.9914.1519857591.27995.bug-bash@gnu.org> |
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 top | Article view | gnu.bash.bug
csiph-web