Re: export of variables and functions

Re: export of variables and functions

[Donn Cave]

>  fn local { unexported=( $unexported $* ) }

I'd use it.

	Donn Cave, University Computing Services, University of Washington
	donn@cac.washington.edu

Re: export of variables and functions

[Chris Siebenmann]

 I actually think that exporting everything is the right decision,
and certainly should be the default. All of my 'local' variables
tend to be function-local, as opposed to shell-local, and we already
have a mechanism for that. How many shell-local variables do people
have/would have?

	- cks

Re: export of variables and functions

[Rich Salz]

Byron and I have exchanged messages about this.  He rightly says that
the default must be to export something, rather than not export it
otherwise old scripts will break.

My idea of unexporting is to have a variable that names the variables to
not be exported.  This seems better then having two new commands, export
and unexport, and makes the "is this variable exported?" test very easy to
write.

fn local { unexported=( $unexported $* ) }
	/r$

export of variables and functions

[malte]

As I read the new man page (1.2) I see that there is still no way not
to export a variable (or function). How about this (which in fact is
borrowed from Wirths Oberon-2): 

	A variable (function) gets exported if its name is immediately
	followed by an '*' or some other char,
	else it is not.

_______________________________________________________________________________
malte@techfak.uni-bielefeld.de

send mail reply to:	Universitaet Bielefeld, Technische Fakultaet
		z. Hd. Malte Uhl
		Postfach 8640
		4800 Bielefeld 1