Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!bloom-beacon!snorkelwacker!usc!wuarchive!texbell!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.tech Subject: Re: SKsh compatibility with unix or AmigaDOS (was: Re: Using PIP:) Keywords: dupping closing pipes Message-ID: <4798@sugar.hackercorp.com> Date: 20 Dec 89 01:36:37 GMT References: <4689@sugar.hackercorp.com> <1610.AA1610@julie> <1718.AA1718@julie> <4780@sugar.hackercorp.com> <1fdu02pp76f901@amdahl.uts.amdahl.com> <1989Dec19.195535.13068@agate.berkeley.edu> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Organization: Sugar Land Unix - Houston Lines: 23 Sorry, I was mixing two subjects: what the shell should do, and what programs should do. Hmmm... maybe AmigaDOS environvent variables should be acessible vi Getenv and Putenv, and UNIX ones via getenv and putenv, by analogy with write/Write, open/Open, etc... This would let your program work both ways. With the Amiga routines as a fallback for getenv/putenv if there's no sksh environment available. Same with options. A program run from the CLI should take Amiga options, run from sksh and it'd take UNIX options. And run from Workbench it would use ToolTypes and WBArgs. An appropriate adaptation of Eric Allman's parseargs sounds like it's in order... Oh, and *I*'m a UNIX-head, too. But I have to deal with intel's daft software development tools that insist on using DOS and iRMX options under UNIX... so I'm sensitive to the problems. -- Peter "Have you hugged your wolf today" da Silva `-_-' 'U` "I haven't lost my mind, it's backed up on tape somewhere"