Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!rutgers!cbmvax!jesup From: jesup@cbmvax.commodore.com (Randell Jesup) Newsgroups: comp.os.misc Subject: Re: shell architecture (to glob or not to glob) Message-ID: <19553@cbmvax.commodore.com> Date: 6 Mar 91 05:02:50 GMT References: <1991Jan14.013815.11419@ims.alaska.edu> <11314@lanl.gov> <0IS9YFC@xds13.ferranti.com> <1991Mar5.171819.10543@watdragon.waterloo.edu> Reply-To: jesup@cbmvax.commodore.com (Randell Jesup) Organization: Commodore, West Chester, PA Lines: 17 In article <1991Mar5.171819.10543@watdragon.waterloo.edu> ccplumb@rose.uwaterloo.ca (Colin Plumb) writes: >Actually, I find that 'command ./filename' works very well, and does >not require much intelligence in the command's option parsing. Yes, "--" >is a standard and should probably be supported, but I've never seen the >need unless you use options that can begin with "." or "/". The problem is (as I stated before, and was misunderstood) that globbing (at least all I've seen) do not force ./path if you don't specify it. So, as I said, you must know what files are going to matched by the glob before you do it. -- 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") ;-)