Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!yale!think!zaphod.mps.ohio-state.edu!van-bc!
From: lphillips@lpami.wimsey.bc.ca (Larry Phillips)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Wildcards, and argument parsing. Re: SKsh completion bug.
Message-ID: <1221@lpami.wimsey.bc.ca>
Date: 9 Mar 90 18:21:00 GMT
Lines: 34
Return-Path: <lpami!lphillips>
To: van-bc!rnews

In <5369@sugar.hackercorp.com>, peter@sugar.hackercorp.com (Peter da Silva) writes:
>
>*when* I get my Amiga back up to multiple megabytes, I'll make parseargs a
>library routine. And provide two versions. So programs that use wildcards
>will be simply able to do:
>
>main(ac, av)
>int ac;
>char **av;
>{
>	parseargs(av, ad);
>
>}
>
>And folks with "unixargs.library" will get UNIX arguments and wildcards, and
>folks with "amiargs.library" will get AmigaDos arguments and wildcards. You
>can already do the argument part with the version of parseargs I sent to
>comp.sources, and getting the wildcards right is just a SMOP.

Wonderful! Looking forward to it. Will you include the option to alow wildcard
matching against arbitrary data? I haven't looked at parseargs yet, so the
above question may reflect that. What I mean is, could I send argv[1] for
expansion against the contents of a directory, and then send argv[2] for
expansion against the expanded argv[1]?

-larry

--
Entymology bugs me.
+-----------------------------------------------------------------------+ 
|   //   Larry Phillips                                                 |
| \X/    lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips |
|        COMPUSERVE: 76703,4322  -or-  76703.4322@compuserve.com        |
+-----------------------------------------------------------------------+