From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Austin-Group discussion of semantics of export, local, etc.
Date: Tue, 09 Nov 2010 09:22:25 -0800 [thread overview]
Message-ID: <101109092225.ZM5090@torch.brasslantern.com> (raw)
Someone who can post to the austin-group list [*] might want to jump in
on this discussion. It started with whether
export foo=bar
should treat foo=bar as an "assignment context" rather than an "argument
context" (zsh currently does the latter) but now has morphed into whether
"local" variables have static or dynamic scoping (Korn is arguing for
standardizing on static, but zsh implements dynamic and relies heavily
on it for the completion function suite).
[*] They've somehow confused my address and effectively rendered me a
read-only participant by not recognizing the origin of any mail I send.
reply other threads:[~2010-11-09 17:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=101109092225.ZM5090@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).