From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@math.gatech.edu
Subject: Re: assoc array memory mucking, and semantics of patterned keys
Date: Tue, 17 Nov 1998 10:42:41 +0100 (MET) [thread overview]
Message-ID: <199811170942.KAA11817@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Peter Stephenson's message of Tue, 17 Nov 1998 09:47:58 +0100
Peter Stephenson wrote:
>
> "Bart Schaefer" wrote:
> > The final possibility is to change the meanings of (r) and (i) when an
> > AA is involved, so that (r) means search the values and (i) means search
> > the keys.
>
> Without thinking too hard, because I want to get some work done today,
> I think I prefer this, because the (k) and (v) flags always refer to
> what's returned, while the (r) and (i) flags always refer to what's
> being searched. It's both neat and powerful. It's maybe annoying
> it's different from normal arrays, but I think understandably so.
> Once you've got the point that (i) tells you to search the index, not
> return it, it's entirely logical. Otherwise the meanings of (k) and
> (i) are mixed in a slightly messy way.
Agreed. Also, I would like to have ${(k)param[(r)pat]} on normal
arrays work like $param[(i)pat] (as Bart suggested in his list). I
probably would even want ${(kv)param[(i)pat]} (and the same with (r))
give a list of indixes and values for normal arrays, just to make
things more consistent.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1998-11-17 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-17 9:42 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-11-16 9:54 Associative arrays and memory Sven Wischnowsky
1998-11-16 12:43 ` Bart Schaefer
1998-11-16 17:16 ` PATCH: 3.1.5: assoc array memory mucking around tedium Peter Stephenson
1998-11-17 8:15 ` assoc array memory mucking, and semantics of patterned keys Bart Schaefer
1998-11-17 8:47 ` Peter Stephenson
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=199811170942.KAA11817@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@math.gatech.edu \
/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).