Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 exptools 1/6/84; site ihuxx.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!ihnp4!ihuxx!ignatz
From: ignatz@ihuxx.UUCP (Dave Ihnat, Chicago, IL)
Newsgroups: net.unix-wizards,net.micro,net.unix
Subject: 'env' rewrite posted to net.sources
Message-ID: <837@ihuxx.UUCP>
Date: Thu, 30-Aug-84 13:41:03 EDT
Article-I.D.: ihuxx.837
Posted: Thu Aug 30 13:41:03 1984
Date-Received: Fri, 31-Aug-84 03:07:57 EDT
Organization: AT&T Bell Labs, Naperville, IL
Lines: 19

I've re-written the 'env' command, in a manner similar to my
rewrite of 'cut' and 'paste'.  As before, no proprietary code
is used.  However, there is one bit of Bell chauvinism which I
perpetuated, through laziness.  Not until Sys V Release 2 did
the existence of 'extern char **environ' become part of documented
Unix(Tm) arcana, although execl(2) and execv(2), even though 'env(1)'
used it before then.  I, also, use it--since it is now documented &
'real'.  I really hope BSD has it, too--or you guys will have to
write the routine to find the executable 'file' from PATH that I
didn't want to write.

Obviously, due to the nature of the command, it isn't really useful
on any micro not running Unix or a Unix shell look-alike; it's more
for people with Unix systems that just don't have the command.

As usual, questions or bug reports (and fixes?) to me.

	Dave Ihnat
	ihuxx!ignatz