Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!jesup
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.arch
Subject: Re: shell architecture (to glob or not to glob)
Message-ID: <19178@cbmvax.commodore.com>
Date: 21 Feb 91 00:56:05 GMT
References: <19062@cbmvax.commodore.com> <1208@sheol.UUCP> <3210@crdos1.crd.ge.COM>
Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
Organization: Commodore, West Chester, PA
Lines: 19

In article <3210@crdos1.crd.ge.COM> davidsen@crdos1.crd.ge.com (bill davidsen) writes:
>  Or write a shell which does nothing but start the process and pass the
>arguemnts... Of course you could just turn globbing off and get the same
>effect. The nice thing is that someone can just go ahead and do this if
>they want. We have sh, csh, ksh (AT&T and PD versions), vcsh, bash,
>clam, and room for more if people think thay need them,

	The problem is that none of the unix utilities do their own
globbing: it wasn't a function in the kernel, and they could always assume
the shell did it.  For example, in AmigaDos (and Stratus VOS), that isn't
the case: there are standard file-pattern-matching and argument parsing
routines that are called by the program.

-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com  BIX: rjesup  
The compiler runs
Like a swift-flowing river
I wait in silence.  (From "The Zen of Programming")  ;-)