Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160209100702.ZM31203@torch.brasslantern.com>
Date: Tue, 9 Feb 2016 10:07:02 -0800
In-Reply-To: <20160209161904.55615638@pwslap01u.europe.root.pri>
Comments: In reply to Peter Stephenson <p.stephenson@samsung.com>
        "Re: unset "hash[key]" isn't matched with what "key" may be" (Feb  9,  4:19pm)
References: <CAKc7PVBXd-UGwM+_tRSwuw-WL154YaTys6-t3iuzfAsG-RC-YQ@mail.gmail.com> 
	<160207133307.ZM31008@torch.brasslantern.com> 
	<160207230544.ZM10065@torch.brasslantern.com> 
	<160208205418.ZM27521@torch.brasslantern.com> 
	<20160209085356.5d9b7401@pwslap01u.europe.root.pri> 
	<160209075050.ZM30873@torch.brasslantern.com> 
	<20160209161904.55615638@pwslap01u.europe.root.pri>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: unset "hash[key]" isn't matched with what "key" may be
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Feb 9,  4:19pm, Peter Stephenson wrote:
}
} getindex() does parse_subcript(); later getarg() looks for tokens and
} if it finds any calls singsub(). "unset" doesn't have any of this
} sophistication.

Hmm.  For a normal array:

torch% x=3
torch% typeset 'foo[$x]'=1
torch% typeset -p foo
typeset -a foo=( '' '' 1 )
torch% unset 'foo[$x]'			<-- Note
torch% typeset -p foo
typeset -a foo=( '' '' '' )
torch% 

It didn't actually delete the element, but it did *something*.  (*Should*
it delete the element, as long as we're considering messing with this?)