Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!bcm!dimacs.rutgers.edu!rutgers!cbmvax!jesup From: jesup@cbmvax.commodore.com (Randell Jesup) Newsgroups: comp.os.misc Subject: Re: Globbing Message-ID: <20057@cbmvax.commodore.com> Date: 23 Mar 91 04:30:30 GMT References: <17602@lanl.gov> <18205@lanl.gov> <18365@lanl.gov> Reply-To: jesup@cbmvax.commodore.com (Randell Jesup) Organization: Commodore, West Chester, PA Lines: 19 In article peter@ficc.ferranti.com (Peter da Silva) writes: >But you don't *know* that only the ultimate consumer is going to expand >wildcards. We're talking about random programs written by random people >at random times for random purposes with random levels of debugging. At >least in UNIX you know that anything you get has been expanded already, >and there is no reason to do so again. If people break the rules, then the rules are broken, and bad things result (at least inconsistency). The same thing happens in Unix, though it's often ignored. If you're designing a system (not Unix) you can design it such that when a wildcarded argument is expanded/processed, all the expanded results are quoted such that the expander won't expand them again. -- 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") ;-)