From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [BUG] ksh_zero_subscript messes with associative arrays
Date: Tue, 26 Jul 2022 17:32:56 +0100 (BST) [thread overview]
Message-ID: <1174358605.42447.1658853176256@mail.virginmedia.com> (raw)
In-Reply-To: <CAMP44s3Os7D51aLZDswRir6j8DhkJVKbfHLH5JoYb-Mz_98WVQ@mail.gmail.com>
> On 26/07/2022 17:18 Felipe Contreras <felipe.contreras@gmail.com> wrote:
> The test is very simple:
>
> setopt ksh_zero_subscript
> typeset -A args
> (( $+args[foo] )) && echo set
>
> ksh_zero_subscript shouldn't be changing the behavior of the code, correct?
I can't see how it should be having any kind of effect on an associative array,
no
pws
diff --git a/Src/params.c b/Src/params.c
index 27ea82298..f587657c7 100644
--- a/Src/params.c
+++ b/Src/params.c
@@ -1996,7 +1996,8 @@ getindex(char **pptr, Value v, int flags)
* altered the start index in getarg().
* Are we being strict?
*/
- if (isset(KSHZEROSUBSCRIPT)) {
+ if (isset(KSHZEROSUBSCRIPT) &&
+ !(v->pm->node.flags & PM_HASHED)) {
/*
* We're not.
* Treat this as accessing the first element of the
diff --git a/Test/D06subscript.ztst b/Test/D06subscript.ztst
index adbd398c4..2546013a9 100644
--- a/Test/D06subscript.ztst
+++ b/Test/D06subscript.ztst
@@ -224,6 +224,11 @@
0:(R) yuckily returns the first element on failure with KSH_ZERO_SUBSCRIPT
>XfimbleX
+ typeset -A empty_hash
+ (( $+empty_hash[unset_param] )) || echo Entry is not set
+0:KSH_ZERO_SUBSCRIPT has no effect on hashes
+>Entry is not set
+
unsetopt KSH_ZERO_SUBSCRIPT
array[(R)notfound,(r)notfound]=(help help here come the seventies retreads)
print $array
next prev parent reply other threads:[~2022-07-26 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 16:18 Felipe Contreras
2022-07-26 16:32 ` Peter Stephenson [this message]
2022-07-26 17:00 ` Bart Schaefer
2022-07-26 17:10 ` Bart Schaefer
2022-07-27 8:21 ` 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=1174358605.42447.1658853176256@mail.virginmedia.com \
--to=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@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).