From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: Bart Schaefer <schaefer@brasslantern.com>, zsh-workers@zsh.org
Subject: Re: Proof of concept: "static" parameter scope
Date: Mon, 5 Oct 2015 21:55:14 +0000 [thread overview]
Message-ID: <20151005215514.GB1959@tarsus.local2> (raw)
In-Reply-To: <20151003201936.29b52aa4@ntlworld.com>
Peter Stephenson wrote on Sat, Oct 03, 2015 at 20:19:36 +0100:
> On Wed, 30 Sep 2015 17:27:48 -0700
> Bart Schaefer <schaefer@brasslantern.com> wrote:
> > Enabling the builtin again does not fix this:
> >
> > torch% enable -r local
> > torch% zxxx
> > zxxx: number expected
>
> Obviously, since it parsed the function zxxx when local wasn't a
> reserved word and you've done nothing to reparse it. You need to parse
> it again.
>
> % enable -r local
> % zxxx() { local x=(a b c); print $x }
> % zxxx
> a b c
Related issue:
% disable -r local
% zxxx() { local x=(a b c); print $x }
% enable -r local
% which zxxx
zxxx () {
local x=(a b c)
print $x
}
Should it output 'builtin local x=(a b c)'?
next prev parent reply other threads:[~2015-10-05 22:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 2:23 Bart Schaefer
2015-09-25 9:15 ` Peter Stephenson
2015-09-26 5:23 ` Bart Schaefer
2015-09-30 19:38 ` Peter Stephenson
2015-10-01 0:27 ` Bart Schaefer
2015-10-03 19:19 ` Peter Stephenson
2015-10-03 23:43 ` Autoloaded keywords (Re: Proof of concept: "static" parameter scope) Bart Schaefer
2015-10-05 21:55 ` Daniel Shahaf [this message]
2015-10-05 22:17 ` Proof of concept: "static" parameter scope Bart Schaefer
2015-10-05 22:36 ` Daniel Shahaf
2015-10-05 23:01 ` Bart Schaefer
2015-10-06 8:40 ` Peter Stephenson
2015-09-28 17:04 ` Oliver Kiddle
2015-09-28 17:58 ` Roman Neuhauser
2015-09-29 23:31 ` Andrew Janke
2015-09-30 3:06 ` Bart Schaefer
2015-09-28 19:42 ` Mikael Magnusson
2015-09-29 1:23 ` Bart Schaefer
2015-09-29 8:39 ` Peter Stephenson
2015-09-29 22:34 ` Daniel Shahaf
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=20151005215514.GB1959@tarsus.local2 \
--to=d.s@daniel.shahaf.name \
--cc=p.w.stephenson@ntlworld.com \
--cc=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).