From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: Proof of concept: "static" parameter scope
Date: Tue, 29 Sep 2015 09:39:05 +0100 [thread overview]
Message-ID: <20150929093905.2d36302e@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <150928182327.ZM29365@torch.brasslantern.com>
On Mon, 28 Sep 2015 18:23:27 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Sep 28, 9:42pm, Mikael Magnusson wrote:
> }
> } What about "private" instead of static though? If the intention is to
> } hide it from called functions, it is somewhat closer to that concept,
> } if not just the normal word.
>
> Once again it's not the same as C++ "private" if that's a concern, but
> I do lean in this direction.
>
> Make up a completely new term? "limited" ? "bounded" ? "scoped" ?
I quite like "private" and I think the C++ meaning is distant enough
that it's not really a confusion. It's the only name that suggests the
scope is limited to right here.
"var" sounds a bit much like the name of a temporary variable.
If you really wanted to emphaise the C connection, the name would be
"auto", but that doesn't make sense for zsh since it doesn't distinguish
static from dynamic scope.
pws
next prev parent reply other threads:[~2015-09-29 8:39 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 ` 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 [this message]
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=20150929093905.2d36302e@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).