From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,e219d94b946dfc26 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news2.google.com!news4.google.com!newsfeed2.dallas1.level3.net!newsfeed1.dallas1.level3.net!news.level3.com!news.binc.net!kilgallen From: Kilgallen@SpamCop.net (Larry Kilgallen) Newsgroups: comp.lang.ada Subject: Re: Ada.Command_Line and wildcards Date: 25 Feb 2007 08:18:15 -0600 Organization: LJK Software Message-ID: References: <45dcaed8_6@news.bluewin.ch> <6w7iu7a5ur.fsf@hod.lan.m-e-leypold.de> NNTP-Posting-Host: eisner.encompasserve.org X-Trace: grandcanyon.binc.net 1172413092 23873 192.135.80.34 (25 Feb 2007 14:18:12 GMT) X-Complaints-To: abuse@binc.net NNTP-Posting-Date: Sun, 25 Feb 2007 14:18:12 +0000 (UTC) Xref: g2news2.google.com comp.lang.ada:9522 Date: 2007-02-25T08:18:15-06:00 List-Id: In article <6w7iu7a5ur.fsf@hod.lan.m-e-leypold.de>, Markus E Leypold writes: > Understand that: This is no question of "how Unix handles the command > line" ore something like this, but simply a question of a specific > choice of syntax for "expand this as a wildcard against the file > system before passing the arguments" taken by the developers of a > specific (though rather standard) shell, the Bourne shell. > > '*.*' -> don't expand > 'abc' -> don't expand > > abc -> expand > *.* -> expand But whether a parameter is a filespec that should be expanded is something known to the program, and the program should make the decision in the absence of user override. Saying the user must specify in all cases is insufficient automation, analogous to weak typing.