From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: wheels within wheels
Date: Tue, 29 Sep 2015 20:24:18 -0700 [thread overview]
Message-ID: <560B55E2.9050606@eastlink.ca> (raw)
In-Reply-To: <CABx2=D_2aXYy1GaZ-d719ZvDQxGD2NwT+KxG7NTwjhGpjkV2OA@mail.gmail.com>
On 09/29/2015 07:55 PM, Kurtis Rader wrote:
> http://unix.stackexchange.com/questions/94129/is-there-something-like-closures-for-zsh
Never heard of it. But thanks for the link. I forget that shells
aren't 'real' languages.
Nuts, I'm even getting used to not declaring variables. As Bart once
said, shells are
a glue for various command line operations.
> In short: don't do it.
I wouldn't, unless there was some sort of wonderful reason to, which is
what I'm asking.
> You can see for yourself that nested, named,
> function definitions are in fact globally visible (as opposed to visible
> only to the function in which they're defined) by executing the following
> script. Anonymous functions defined within another function are a different
> matter but outside the scope of this question.
Yeah, I ran my own tests and it seems so. One might think that this
would be some sort of
localization mechanism, but it seems not to be the case. Ok, thanks
Kurtis, I'll not
try any such thing. It seems very strange that it's even legal.
next prev parent reply other threads:[~2015-09-30 3:54 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 15:54 autoload Ray Andrews
2015-09-17 17:34 ` autoload Bart Schaefer
2015-09-17 19:22 ` autoload Ray Andrews
2015-09-17 20:40 ` autoload Bart Schaefer
2015-09-17 23:06 ` autoload Ray Andrews
2015-09-17 23:20 ` autoload Bart Schaefer
2015-09-18 1:20 ` autoload Ray Andrews
2015-09-18 4:04 ` autoload Bart Schaefer
2015-09-18 5:00 ` autoload Ray Andrews
2015-09-18 5:52 ` autoload Bart Schaefer
2015-09-18 15:49 ` autoload Ray Andrews
2015-09-18 16:52 ` autoload Bart Schaefer
2015-09-18 18:29 ` autoload Ray Andrews
2015-09-18 19:02 ` autoload Bart Schaefer
2015-09-18 22:57 ` autoload Ray Andrews
2015-09-19 0:14 ` autoload Bart Schaefer
2015-09-19 15:04 ` autoload Ray Andrews
2015-09-19 16:29 ` autoload Bart Schaefer
2015-09-19 18:13 ` autoload Ray Andrews
2015-09-19 21:22 ` autoload Bart Schaefer
2015-09-19 22:12 ` autoload Ray Andrews
2015-09-20 5:53 ` autoload Bart Schaefer
2015-09-20 15:37 ` autoload Ray Andrews
2015-09-20 15:59 ` autoload Bart Schaefer
2015-09-20 0:58 ` autoload Ray Andrews
2015-09-20 5:41 ` autoload Bart Schaefer
2015-09-20 23:21 ` autoload Ray Andrews
2015-09-21 4:18 ` autoload Bart Schaefer
2015-09-21 17:03 ` autoload Ray Andrews
2015-09-21 18:17 ` autoload Bart Schaefer
2015-09-21 20:09 ` autoload Ray Andrews
2015-09-22 3:19 ` autoload Bart Schaefer
2015-09-22 17:33 ` autoload Ray Andrews
2015-09-23 4:39 ` autoload Bart Schaefer
2015-09-23 15:06 ` autoload Ray Andrews
2015-09-29 23:16 ` wheels within wheels Ray Andrews
2015-09-30 2:55 ` Kurtis Rader
2015-09-30 3:24 ` Ray Andrews [this message]
2015-09-30 3:40 ` Bart Schaefer
2015-09-30 4:03 ` Mikael Magnusson
2015-09-30 4:15 ` Ray Andrews
2015-09-30 7:05 ` Bart Schaefer
2015-09-30 15:06 ` Ray Andrews
2015-09-30 8:01 ` ZyX
2015-09-30 15:18 ` Ray Andrews
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=560B55E2.9050606@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@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).