zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: [PATCH] More rigorous subscript checking in named references
Date: Sun, 12 Feb 2023 12:16:06 -0800	[thread overview]
Message-ID: <CAH+w=7Y5Jz0EC2M1NB0fZ_a9S5L=VJ-ARC06Qsg6zNTJRm8Vtw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 229 bytes --]

The first 7 named ref patches have been pushed, so there ends the
increasingly inaccurately named patch trilogy, at least in the subject
lines.

This covers the case Oliver called out, of extra stuff following a
valid subscript.

[-- Attachment #2: nameref-8-subscripts.txt --]
[-- Type: text/plain, Size: 1064 bytes --]

diff --git a/Src/params.c b/Src/params.c
index 4910d65fe..f61374b87 100644
--- a/Src/params.c
+++ b/Src/params.c
@@ -6281,7 +6281,16 @@ valid_refname(char *val)
     if (*t != 0) {
 	if (*t == '[') {
 	    tokenize(t = dupstring(t+1));
-	    t = parse_subscript(t, 0, ']');
+	    while ((t = parse_subscript(t, 0, ']')) && *t++ == Outbrack) {
+		if (*t == Inbrack)
+		    ++t;
+		else
+		    break;
+	    }
+	    if (t && *t) {
+		/* zwarn("%s: stuff after subscript: %s", val, t); */
+		t = NULL;
+	    }
 	} else if (t[1] || !(*t == '!' || *t == '?' ||
 			     *t == '$' || *t == '-' ||
 			     *t == '0' || *t == '_')) {
diff --git a/Test/K01nameref.ztst b/Test/K01nameref.ztst
index 61c2b006a..d2abdd391 100644
--- a/Test/K01nameref.ztst
+++ b/Test/K01nameref.ztst
@@ -350,9 +350,9 @@ F:ksh93 does not implement this either
 >typeset -A hash=( [y]=HIT )
 
  unset -n ptr1
- typeset -n ptr1='not good'
+ typeset -n ptr1='not[2]good'
 1:invalid nameref
-*?*invalid variable name: not good
+*?*invalid variable name: not\[2\]good
 
  unset -n ptr1
  unset hash

             reply	other threads:[~2023-02-12 20:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-12 20:16 Bart Schaefer [this message]
2023-02-12 23:13 ` 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='CAH+w=7Y5Jz0EC2M1NB0fZ_a9S5L=VJ-ARC06Qsg6zNTJRm8Vtw@mail.gmail.com' \
    --to=schaefer@brasslantern.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).