Path: utzoo!attcan!uunet!cbmvax!daveh From: daveh@cbmvax.commodore.com (Dave Haynie) Newsgroups: comp.sys.amiga.tech Subject: Re: Wildcards Message-ID: <10247@cbmvax.commodore.com> Date: 19 Mar 90 17:16:59 GMT References: <102618@linus.UUCP> <5405@sugar.hackercorp.com> Reply-To: daveh@cbmvax (Dave Haynie) Organization: Commodore, West Chester, PA Lines: 27 In article deven@rpi.edu (Deven T. Corzine) writes: >In response to Dave Haynie's note that "*" has special meaning to >AmigaDOS: point taken. But there are times it can be determined from >context whether "*" should be the console or a wildcard. I agreed with the use of "|" as a pipe character in WShell for the same basic reason, once WShell was taught that "thing | thing" should mean pipe, while "thing|thing" should mean pattern alternation. >Of course, there are situations where it is indeterminable. Offering the >user a configurable option of whether or not to treat "*" as a wildcard, >and permit it to be escaped with \ or even *. Well, then, how about a general facility in the shell to add read macros. Then you get the system in standard form, but if you want, add a read macro that converts "*" to "#?" at the shell level. Of course, what you really want is such a facility below the shell level, so the same conversions take place in file requesters or any other place wild card expansion (at least when provided via standard system calls) takes place. >Deven -- Dave Haynie Commodore-Amiga (Systems Engineering) "The Crew That Never Rests" {uunet|pyramid|rutgers}!cbmvax!daveh PLINK: hazy BIX: hazy Too much of everything is just enough