From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Example function
Date: Mon, 1 Feb 1999 11:48:11 +0100 (MET) [thread overview]
Message-ID: <199902011048.LAA07559@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Tue, 26 Jan 1999 16:37:43 -0800
Bart Schaefer wrote:
> (One of the things on the associative-array wishlist is "reverse pattern"
> lookup, that is, treat the array keys as patterns and match them against
> the subscript. Then you could do silly stuff like
>
> typeset -A map
> map=('*.(gz|Z)' zcat
> '*.bz2' 'bzip2 -dc'
> '*.bz' 'bzip -dc'
> '*' '<')
> eval ${(q)map[$argv[i]]} '$argv[i]'
>
> where I'm using (q) as the fictional reverse-pattern query flag; probably
> there's a better letter.)
>
> Incidentally, the reason this isn't there already is that associative arrays
> are unordered hashes, so you can't predict _which_ pattern will match the
> subscript when you do the query -- '*' might match before '*.bz' is tried.
I was thinking about this... we could make the code keep a counter in
assoc arrays, increment it whenever a new key is added and store the
current value in the structure for this new element. Then we can treat
the whole thing as being sorted by `time of addition'.
Hm, does this sound like the right thing?
Bye
Sven
P.S.: Is `foo=( ${(kv)foo[(I)^key]} )' the easiest way to remove a
key/value-pair from an associative array?
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-02-01 10:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-01 10:48 Sven Wischnowsky [this message]
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
-- strict thread matches above, loose matches on Subject: below --
1999-01-26 18:42 Example function Phil Pennock
1999-01-27 0:25 ` Bart Schaefer
1999-01-27 0:37 ` Bart Schaefer
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=199902011048.LAA07559@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).