Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!umd5!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.wizards
Subject: Re: command line options
Message-ID: <7764@brl-smoke.ARPA>
Date: 25 Apr 88 21:53:52 GMT
References: <2414@zyx.UUCP> <8039@elsie.UUCP> <7628@brl-smoke.ARPA> <143@gsg.UUCP> <7634@brl-smoke.ARPA> <1864@sugar.UUCP> <7746@brl-smoke.ARPA> <2075@quacky.mips.COM>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 11

In article <2075@quacky.mips.COM> dce@quacky.UUCP (David Elliott) writes:
>In article <7746@brl-smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
>>In the 8th Edition UNIX shell, you simply export them via the environment.
>How do shell scripts handle this situation?
>Do I have to do "unset" (or otherwise undefine) each name that I use,

Basically the answer would seem to be "yes".
That's one reason I decided to take a different approach
for the BRL Bourne shell.
The other problem is that most existing Bourne shells die a
horrible death when the environment contains anything other
than NAME=VALUE pairs.