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: g2news1.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: 9 Mar 2007 12:58:21 -0600 Organization: LJK Software Message-ID: References: <45dcaed8_6@news.bluewin.ch> NNTP-Posting-Host: eisner.encompasserve.org X-Trace: grandcanyon.binc.net 1173466615 24344 192.135.80.34 (9 Mar 2007 18:56:55 GMT) X-Complaints-To: abuse@binc.net NNTP-Posting-Date: Fri, 9 Mar 2007 18:56:55 +0000 (UTC) Xref: g2news1.google.com comp.lang.ada:14437 Date: 2007-03-09T12:58:21-06:00 List-Id: In article , Markus E Leypold writes: > > rdeininger@mindspringdot.com (Robert Deininger) writes: > >> In article <11wk29zr0.fsf@hod.lan.m-e-leypold.de>, Markus E Leypold >> wrote: >>> - I do think the VMS shell has the same problem with the difference between >>> >>> foo yadda*.* >>> >>> and >>> >>> foo yadda *.* >> >> Out of curiosity, what is the problem here in VMS? >> >> The first example passes 1 parameter (yadda*.*) to the command foo. If > >> The second example passes 2 parameters (yadda and *.*) to command foo. If > > To me, none. It was the role of space as argument separator some > people have been complaining about, see the post before my reply. What constitutes an argument separator depends on the definition of the command language being used. VMS defines unquoted spaces in DCL commands as separating arguments. If one is bound and determined to create a program that flies in the face of what users are expecting on VMS, the Foreign Command mechanism can be used.