From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: uninvited members of associative array
Date: Fri, 16 Dec 2022 06:13:45 -0800 [thread overview]
Message-ID: <902fb047-3435-89a3-e7ea-74e74075c2c6@eastlink.ca> (raw)
In-Reply-To: <Y5xC5vQCjJwm9jsw@localhost>
On 2022-12-16 02:05, Dominik Vogt wrote:
>
> The issue is not solved. You still have something that adds the
> bogus values before the reinitialisation. Whether this has some
> adverse effects depends on the scripts. (Sample script attached).
> Basically you probably do ~ this:
True Dominik, it's not solved, I should rather say I can put it on ice
for a while while I attend to another issue more pressing. I will get
back to it and I'll let you all know what I found. It is probably
exactly as yourself and Bart suspect. I will catch it.
Roman:
I just want to point out that in general you need to quote the array
expansion here or you'll get surprises if the array has empty keys
and/or values. Consider this:
typeset -A main=(
foo '1'
bar '2'
baz ''
qux ''
)
printf '%-4s = %s\n' ${(kv)main}
And the output:
foo = 1
baz = bar
2 = qux
... this is exactly the sort of thing I was talking to Lawrence about --
not really a hard error, just some printout issue. I'll pursue that. I
(think I) understand that AAs are very fragile creatures and as you
demonstrate, easily confused. I'll bag it.
next prev parent reply other threads:[~2022-12-16 14:15 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 23:48 Ray Andrews
2022-12-16 0:05 ` Lawrence Velázquez
2022-12-16 0:48 ` Ray Andrews
2022-12-16 1:29 ` Lawrence Velázquez
2022-12-16 2:09 ` Dominik Vogt
2022-12-16 2:56 ` Ray Andrews
2022-12-16 3:21 ` Lawrence Velázquez
2022-12-16 4:16 ` Ray Andrews
2022-12-16 10:05 ` Dominik Vogt
2022-12-16 14:13 ` Ray Andrews [this message]
2022-12-16 15:19 ` Dominik Vogt
2022-12-16 19:14 ` Ray Andrews
2022-12-16 16:30 ` Daniel Shahaf
2022-12-16 18:21 ` Ray Andrews
2022-12-16 19:04 ` Dominik Vogt
2022-12-16 20:10 ` Ray Andrews
2022-12-16 21:15 ` Dominik Vogt
2022-12-16 21:33 ` Bart Schaefer
2022-12-16 21:59 ` Dominik Vogt
2022-12-16 22:15 ` Bart Schaefer
2022-12-16 23:33 ` Ray Andrews
2022-12-17 12:47 ` Pier Paolo Grassi
2022-12-17 17:32 ` Ray Andrews
2022-12-17 18:10 ` Ray Andrews
2022-12-17 18:19 ` Roman Perepelitsa
2022-12-17 20:31 ` Ray Andrews
2022-12-17 20:49 ` Bart Schaefer
2022-12-17 21:07 ` Lawrence Velázquez
2022-12-17 21:52 ` Ray Andrews
2022-12-17 22:10 ` Bart Schaefer
2022-12-17 23:41 ` Daniel Shahaf
2022-12-18 0:15 ` Ray Andrews
2022-12-18 0:25 ` Daniel Shahaf
2022-12-18 2:13 ` Ray Andrews
2022-12-18 20:12 ` Daniel Shahaf
2022-12-18 20:26 ` Bart Schaefer
2022-12-18 20:41 ` Ray Andrews
2022-12-18 3:44 ` Lawrence Velázquez
2022-12-17 23:25 ` Daniel Shahaf
2022-12-16 21:33 ` Ray Andrews
2022-12-16 20:25 ` Daniel Shahaf
2022-12-16 21:43 ` Dominik Vogt
2022-12-16 3:20 ` Bart Schaefer
2022-12-16 4:15 ` Ray Andrews
2022-12-16 8:12 ` Roman Perepelitsa
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=902fb047-3435-89a3-e7ea-74e74075c2c6@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.org \
/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).