From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Associative array ordering and selective unset (Re: Example function)
Date: Tue, 2 Feb 1999 08:52:20 +0100 (MET) [thread overview]
Message-ID: <199902020752.IAA08445@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Mon, 1 Feb 1999 09:02:46 -0800
Bart Schaefer wrote:
> ...
>
> We could go the ksh route and make `noglob unset foo[key]` work. Like:
>
> function unset() {
> emulate -R zsh
> setopt localoptions extendedglob
> local arg i
> for i
> do
> arg=( "${(@s:[:)i}" )
> if [[ $#arg > 1 &&
> $(eval print '${(t)'${arg[1]}'}') == association ]]
> then
> eval "$arg[1]=( \${(kv)$arg[1][(I)^${(j:[:)arg[2,-1]} )"
> else
> builtin unset $i
> fi
> done
> }
Since even `vared' can now understand the subscripted syntax, I think
adding this to unset (even in C) would be a good thing. (I'm pretty
sure people will want to have a easy way to remove key/value-pairs
from associative arrays).
> Can you think of a better idiom than $(eval print '${(t)'${arg[1]}'}') to
> get the type of the variable whose name is the value of $arg[1] ? I keep
> thinking there ought to be a way with ${(e)...} but couldn't make it work.
When implementing the new completion example stuff I was somewhat
irritated that there is no easy way to get the value of a parameter of
which one only has the name in another parameter. Trying to get the
type of that parameter is indeed even more complicated.
Hm, `(e)' is used at the very end and I wouldn't like to change
that. Maybe yet another flag? E.g.: `P' makes the thing after the
flags be used as the name of a parameter. So `${(P)foo}' is the same
as `$foo', but `${(P)${foo}}' will take the value of `foo' as the name
of a parameter and work on it. So your example would become:
if [[ $#arg > 1 && ${(Pt)${argv[1]}} == association ]] ...
Looking at the code this doesn't seem too hard to implement (well, I
said `seem'...).
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-02-02 7:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-02 7:52 Sven Wischnowsky [this message]
1999-02-02 11:10 ` PATCH: 3.1.5-pws-6: unset assoc[key] Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
1999-02-02 16:58 Associative array ordering and selective unset (Re: Example function) Sven Wischnowsky
1999-02-02 8:01 Sven Wischnowsky
1999-02-01 10:48 Example function Sven Wischnowsky
1999-02-01 17:02 ` Associative array ordering and selective unset (Re: Example function) Bart Schaefer
1999-02-01 17:39 ` Bruce Stephens
1999-02-01 19:09 ` Bart Schaefer
1999-02-02 20:07 ` Phil Pennock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199902020752.IAA08445@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).