zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Bug in alias expansion
Date: Sun, 15 Nov 2015 13:52:18 -0800	[thread overview]
Message-ID: <151115135218.ZM25449@torch.brasslantern.com> (raw)
In-Reply-To: <20151115200356.0f3a80a2@ntlworld.com>

On Nov 15,  8:03pm, Peter Stephenson wrote:
}
} On Fri, 13 Nov 2015 13:03:52 -0500
} Kynn Jones <kynnjo@gmail.com> wrote:
} > % typeset -A frobozz
} > % alias -g foo='echo xyz'
} > % frobozz[$(foo)]=9
} > zsh: not an identifier: frobozz[$(fooech9
} 
} This is somewhere in the vicinity of parse_subscript().  That's called
} both from isident() and getindex(); I got as far as the case called from
} isident(), but it may be the second one gets called, too.

[...]

} I don't know why this works in other contexts.

When called from "typeset frobozz[$(foo)]=9" the ($foo) has been expanded
before parse_subscript() is called the first time [via isident()]:

Breakpoint 1, parse_subscript (s=0xb7d919e8 "xyz]", sub=1, endchar=93)
    at ../../zsh-5.0/Src/lex.c:1620

When called as a plain assignment without the "typeset" keyword, $(foo)
has not yet been expanded:

Breakpoint 1, parse_subscript (s=0xb7d917f8 "$(foo)]", sub=1, endchar=93)
    at ../../zsh-5.0/Src/lex.c:1620

This call is originating from addvars():

#0  parse_subscript (s=0xb7d91820 "$(foo)]", sub=1, endchar=93)
    at ../../zsh-5.0/Src/lex.c:1620
#1  0x080b2334 in isident (s=0xb7d91818 "frobozz[$(foo)]")
    at ../../zsh-5.0/Src/params.c:1078
#2  0x080b6660 in assignsparam (s=0xb7d91818 "frobozz[$(foo)]", 
    val=0x88bbdf0 "9", flags=0) at ../../zsh-5.0/Src/params.c:2741
#3  0x08078342 in addvars (state=0xbfe30f70, pc=0xb7d917a8, addflags=0)
    at ../../zsh-5.0/Src/exec.c:2348
#4  0x08074dff in execsimple (state=0xbfe30f70)
    at ../../zsh-5.0/Src/exec.c:1118

So the real question may be, how did we get as far as execsimple()
without having expanded all the aliases first?


  reply	other threads:[~2015-11-15 21:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13 18:03 Kynn Jones
2015-11-14  1:03 ` Bart Schaefer
2015-11-14 18:57   ` Kynn Jones
2015-11-14 19:03     ` Bart Schaefer
2015-11-14 19:19       ` Kynn Jones
2015-11-14 21:40         ` Bart Schaefer
2015-11-14 22:20           ` Kynn Jones
2015-11-15 20:03 ` Peter Stephenson
2015-11-15 21:52   ` Bart Schaefer [this message]
2015-11-15 22:26     ` Bart Schaefer
2015-11-15 22:48   ` Bart Schaefer
2015-11-16  0:50     ` Mikael Magnusson
2015-11-16  3:24       ` Bart Schaefer
2015-11-16  5:42         ` Mikael Magnusson
2015-11-18 10:42     ` Peter Stephenson
2015-11-18 14:13       ` Peter Stephenson
2015-11-18 15:52         ` Bart Schaefer
2015-11-18 16:14           ` Peter Stephenson
2015-11-18 18:09             ` Bart Schaefer
2015-11-17 17:29   ` Peter Stephenson
2015-11-18  4:55     ` Bart Schaefer
2015-11-18 10:30       ` 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=151115135218.ZM25449@torch.brasslantern.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).