Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!bywater!arnor!prener!prener
From: prener@arnor.UUCP (Dan Prener)
Newsgroups: comp.unix.aix
Subject: Re: Using ksh set -u breaks xinit script...
Message-ID: <1991Mar28.012949.1375@arnor.uucp>
Date: 28 Mar 91 01:29:49 GMT
References: <1991Mar26.051930.16308@panix.uucp>
Sender: news@arnor.uucp (NNTP News Poster)
Reply-To: prener@prener.watson.ibm.com (Dan Prener)
Organization: IBM T.J. Watson Research Center
Lines: 8

If all uses of undefined shell variables are to be considered errors,
then it becomes very difficult to get first-time switches and to
keep other state.  How, for example does shell script s1 tell whether
shell script s2 has been executed?  Isn't this usually done by testing
some shell variable that will have been set by s2, or left unset if
s2 has not been executed?
-- 
                                   Dan Prener (prener @ watson.ibm.com)