zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: SourceForge bug id 104052 - case study.
Date: Tue, 15 Aug 2000 19:36:38 +0400	[thread overview]
Message-ID: <000401c006ce$9a5e8810$21c9ca95@mow.siemens.ru> (raw)

May be, it is well known already.

There are at least three different cases covered by this bug:

Case 1.

bor@itsrm2% typeset -A foo
bor@itsrm2% foo[\]]=bar
zsh: not an identifier: foo[\]]

Case 2.

bor@itsrm2% print $foo[\]]
]
bor@itsrm2% print ${foo[\]]}
zsh: bad substitution

Case 3.

bor@itsrm2% print $foo[(I)[^]]]
bar] <== that I do not understand at all!
bor@itsrm2% print ${(kv)foo}
a bar abc baz

Case 1 is caused by the fact, that setsparam() gets unmetafied parameter name.
Ironically, in this case everything is correctly parsed, `]' is properly
quoted, but distinction between `]' and `\]' is lost when parameter is
unmetafied. setsparam() calls isident(), that just checks for balanced `[' and
`]' and barfs (it never checks what is really inside the brackets).

Case 2 comes from the fact, that paramsubst() and getindex() treat both quoted
and unquoted brackets the same. The reason is (as I suspect) parameter
substitution in double-quotes - "$foo[bar]". When it is parsed by
dquote_parse(), it adds just plain ']' and not Outbrack; so, when it finally
reaches paramsubst() it may encounter both values. When inside of parens, Zsh
just warns about missing closing one (because it finds end of substitution too
early).

Case 3 the problem seems to be getarg(). It blindly skips over balanced
brackets that is of course wrong in this case.

Case 1 is basically independent of other two. Unfortunately, to solve it we
need to either remove call to isident() in setsparam() or pass metafied
parameter name to setsparam() and make isident() smart enough.

Case 2 - lexer should return different token for "]" as for \], e.g. Qoutbrack
like Qstring. And, of course, all uses of ']'/Outbrack should be checked ...
but note, that in this case

$foo[\]]

will be valid, but

"$foo[\]]"

not. By definition, you cannot quote inside of double quotes. Even

$foo["]"]

will be invalid in this case (a bit unexpected), unless code can be smart
enough to notice, that initial Inbrack was not quoted.

Case 3 - we may try to change (getarg(), around line 916 in Src/params.c)

	else if (c == ']' || c == Outbrack)

into something like

	else if ((c == ']' || c == Outbrack) &&
                t[-1] != '^' && t[-1] != '!' && t[-2] != '[' && t[-2] !=
Inbrack)

but this highly ambiguous case remains

$foo[(I)$bar[^]]

-andrej


             reply	other threads:[~2000-08-15 15:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-15 15:36 Andrej Borsenkow [this message]
2000-08-18  9:12 ` Question " Andrej Borsenkow

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='000401c006ce$9a5e8810$21c9ca95@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --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).