From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: Proof of concept: "static" parameter scope
Date: Fri, 25 Sep 2015 10:15:40 +0100 [thread overview]
Message-ID: <20150925101540.5d2ded9c@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <150924192305.ZM2680@torch.brasslantern.com>
On Thu, 24 Sep 2015 19:23:05 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> Modules can't declare keywords, so this isn't able to support the new
> array assignment syntax used by "local" et al. However, the entry point
> is coded to match that call signature.
I think the biggest issue with fixing this is it's going to change the
"features" interface to modules as we'll have to add a feature type that
defines a typeset-style interface (and a corresponding reserved word,
but I think we can tie the two together). But fiddling with the system
to get a module added is already tough enough that that may not cause
much real practical trouble.
Typically, I think modules would then do what "typeset" effectively does
(hard-wired rather than via features) and declare both a builtin and an
enhanced version as separate features, and we should probably mention
this in the development guidelines.
Not sure what to do about printparamnode().
pws
next prev parent reply other threads:[~2015-09-25 9:15 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 [this message]
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 ` Proof of concept: "static" parameter scope Daniel Shahaf
2015-10-05 22:17 ` 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=20150925101540.5d2ded9c@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.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).