From: Chris Jepeway <jepeway@blasted-heath.com>
To: chet@po.CWRU.Edu
Cc: zsh-users@sunsite.dk, pws@csr.com
Subject: Re: ksh Emulation Not Clearing Envariables
Date: Tue, 11 May 2004 14:44:28 -0400 [thread overview]
Message-ID: <3BDC51C1-A37B-11D8-B3B9-000A95B34D8E@blasted-heath.com> (raw)
In-Reply-To: <040511181944.AA29985.SM@caleb.ins.cwru.edu>
>>> POSIX wants the envariable to persist across invocations
>>> of the function "e"? That seems...counter-intuitive.
>>
>> I can't find it in POSIX now, but it's controlled by the option
>> posix_builtins. We could turn that off for ksh, but I'd like to know
>> if
>> we really ever need to have it on by default.
>
> http://www.opengroup.org/onlinepubs/009695399/utilities/
> xcu_chap02.html#tag_02_09_05
>
> Where we see
>
> When a function is executed, it shall have the syntax-error and
> variable-assignment properties described for special built-in
> utilities in the enumerated list at the beginning of Special Built-In
> Utilities.
>
> One of those properties is:
>
> Variable assignments specified with special built-in utilities remain
> in effect after the built-in completes; this shall not be the case
> with a regular built-in or other utility.
Well...the variable assignment isn't occurring inside the function.
It's outside, put into the environment before the function is called.
Had the function looked like:
e() {
X=one
echo $X
}
e ; echo "[$X]"
I would have expected to see
one
[one]
However, with this:
e() {
echo $X
}
X=one e ; echo "[$X]"
I'd expect to see
one
[]
I don't see how the spec can be read to mean "envariables
poked into a command shall persist across command invocations
when that command is a shell function."
> Chet Ramey, ITS, CWRU chet@po.cwru.edu
> http://tiswww.tis.cwru.edu/~chet/
Chris.
next prev parent reply other threads:[~2004-05-11 18:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-09 0:41 Chris Jepeway
2004-05-09 21:58 ` Bart Schaefer
2004-05-10 14:52 ` Peter Stephenson
2004-05-11 17:03 ` Chris Jepeway
2004-05-11 16:59 ` Chris Jepeway
2004-05-11 17:34 ` Peter Stephenson
[not found] ` <040511181944.AA29985.SM@caleb.ins.cwru.edu>
2004-05-11 18:44 ` Chris Jepeway [this message]
2004-05-11 20:22 ` Bart Schaefer
[not found] ` <040511192759.AA02456.SM@caleb.ins.cwru.edu>
2004-05-11 20:38 ` Chris Jepeway
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=3BDC51C1-A37B-11D8-B3B9-000A95B34D8E@blasted-heath.com \
--to=jepeway@blasted-heath.com \
--cc=chet@po.CWRU.Edu \
--cc=pws@csr.com \
--cc=zsh-users@sunsite.dk \
/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).