zsh-workers
 help / color / mirror / code / Atom feed
* Environment Passed to Functions
@ 1995-06-14 20:17 Vinnie Shelton
  1995-06-15  8:46 ` P.Stephenson
  0 siblings, 1 reply; 2+ messages in thread
From: Vinnie Shelton @ 1995-06-14 20:17 UTC (permalink / raw)
  To: zsh-workers

If an environment variable is set on the command line for a function, then 
that enviroment variable is only in effect for the first command in the 
function.  ksh handles this differently; the variable is in the environment 
for all the commands in the function.  E.g.

~ Wed 14 16:08 % echo $ZSH_VERSION 
2.6-beta9
~ Wed 14 16:12 % echo $LPDEST
 
~ Wed 14 16:13 % function foo {
> env >/dev/null
> env
> }
~ Wed 14 16:13 % LPDEST=foo foo | grep LPDEST
~ Wed 14 16:14 % 

LPDEST is not set.  Now for ksh:

~ Wed 14 16:15 % ksh
$ echo $LPDEST
 
$ function foo {
> env >/dev/null
> env
> }
$ LPDEST=foo foo | grep LPDEST
LPDEST=foo
$ 

I think the ksh behavior is more useful - it makes a function's environment 
more like a shell script's.  Opinions?

--Vin


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~1995-06-15  8:59 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1995-06-14 20:17 Environment Passed to Functions Vinnie Shelton
1995-06-15  8:46 ` P.Stephenson

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).