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 Newsgroups: comp.lang.ada Subject: Re: Ada.Command_Line and wildcards References: <45dcaed8_6@news.bluewin.ch> <1172132169.423514.271890@s48g2000cws.googlegroups.com> <545bgvF1ttrphU1@mid.individual.net> <1495406.QZvfpqijrQ@linux1.krischik.com> <6dy7mn3hhu.fsf@hod.lan.m-e-leypold.de> <1172328891.5496.62.camel@localhost.localdomain> <1173096982.3712.37.camel@localhost> <8utzwzzv0v.fsf@hod.lan.m-e-leypold.de> <1173185771.11841.69.camel@localhost> <11wk29zr0.fsf@hod.lan.m-e-leypold.de> From: Markus E Leypold Organization: N/A Date: Fri, 09 Mar 2007 18:15:39 +0100 Message-ID: User-Agent: Some cool user agent (SCUG) Cancel-Lock: sha1:q4aPolhdDfXpfSikHutLGB1b/WQ= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii NNTP-Posting-Host: 88.72.201.211 X-Trace: news.arcor-ip.de 1173460164 88.72.201.211 (9 Mar 2007 18:09:24 +0200) X-Complaints-To: abuse@arcor-ip.de Path: g2news1.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsfeed.arcor-ip.de!news.arcor-ip.de!not-for-mail Xref: g2news1.google.com comp.lang.ada:14434 Date: 2007-03-09T18:15:39+01:00 List-Id: rdeininger@mindspringdot.com (Robert Deininger) writes: > In article <11wk29zr0.fsf@hod.lan.m-e-leypold.de>, Markus E Leypold > wrote: > > ... > >>As far as the shell syntax is concerned: >> > ... >> >> - 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. > If this behavior isn't reasonable, what behavior would be? Ask me. I should have set "problem" in quotes. > Auto-correcting of typos, with a mind-reading option? Hey, wasn't me who styled that as a problem ... >>Yes, but the brokenness of the auto configuration philosophy has >>nothing to do with Unix design choices. It is actually a problem VMS >>wouldn't have, since it doesn't exist in different sizes on vastly >>different platforms. > > VMS certainly does exist in different sizes on different platforms. But > the OS does a good job of hiding most of the underlying platform from > applications, so they don't need to care. There is only so much you can hide if the underlying platform is really different. Emulating a 32bit enviroment on a 16bit plattform would be tedious, restricting a 32bit platform to a 16bit "portable" API dito. > Auto-configuration style hacks are rarely used in native VMS > applications. Usually, the information the hack is trying to figure out > can be obtained more directly. > > Importing autoconfiguration hacks to VMS can be a nightmare. :-) Regards -- Markus