Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!van-bc!
From: lphillips@lpami.wimsey.bc.ca (Larry Phillips)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Ok, so how about * = #?
Message-ID: <2223@lpami.wimsey.bc.ca>
Date: 13 Nov 90 21:55:58 GMT
Lines: 30
Return-Path: <lpami!lphillips>
To: van-bc!rnews

In <26889.273fce5f@kuhub.cc.ukans.edu>, markv@kuhub.cc.ukans.edu writes:
>>I've been hearing alot about the * = #? option of the 2.0 OS.  Something about
>> setting a bit somewhere, and Voila! you can now use * for a #?.  How?
>
>The problem with *=#? is one I am dealing with in a program and is one
>of my gripes with #? in general.  #? isn't quite like * because #?
>requires at least one charecter.  So if I have a dir like:
>
>	Program	Program.c Program.o Program.info Progranny
>
>If I want all the files for Program, I cant do "dir Program#?" because
>I wont match Program.  On the otherhand if I do "dir Progra#?" its a
>kludge because I have to keep from typing the last char, and I might
>get files I don't care about, like Progranny.  (I realize this is a
>dumb example, but it makes my point).

Say what? Both in the spec (#? means match 0 or more occurrences of any
character), and by observed operation, 'dir Program#?' will indeed match all of
the items you mentioned except 'Progranny'. At least it has worked this way for
me for as long as I can remember.

-larry

--
The only things to survive a nuclear war will be cockroaches and IBM PCs.
+-----------------------------------------------------------------------+ 
|   //   Larry Phillips                                                 |
| \X/    lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips |
|        COMPUSERVE: 76703,4322  -or-  76703.4322@compuserve.com        |
+-----------------------------------------------------------------------+