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!newshub.sdsu.edu!elnk-nf2-pas!newsfeed.earthlink.net!stamper.news.pas.earthlink.net!newsread4.news.pas.earthlink.net.POSTED!3e051fae!not-for-mail From: rdeininger@mindspringdot.com (Robert Deininger) Newsgroups: comp.lang.ada Subject: Re: Ada.Command_Line and wildcards Message-ID: 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> Date: Fri, 09 Mar 2007 13:41:00 GMT NNTP-Posting-Host: 4.233.173.137 X-Complaints-To: abuse@earthlink.net X-Trace: newsread4.news.pas.earthlink.net 1173447660 4.233.173.137 (Fri, 09 Mar 2007 05:41:00 PST) NNTP-Posting-Date: Fri, 09 Mar 2007 05:41:00 PST Organization: EarthLink Inc. -- http://www.EarthLink.net Xref: g2news1.google.com comp.lang.ada:14432 Date: 2007-03-09T13:41:00+00:00 List-Id: 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 number of required parameters for foo is <= 1, it will run. Otherwise, the shell will prompt for more parameters. The second example passes 2 parameters (yadda and *.*) to command foo. If foo is defined with only 1 parameter, the shell will report a "too many parameters" error instead of invoking foo. If this behavior isn't reasonable, what behavior would be? Auto-correcting of typos, with a mind-reading option? $ SET PROCESS/PARSE_STYLE=READ_MIND Of course, the default would have to be /PARSE_STYLE=NOREAD_MIND to maintain upward compatibility. :-) ... >>> Most (auto-) configuration concepts are really bad hacks. They are >>> hardly Unix design choices. The wrong place to fix that is to change >>> the shell or the prcess model. > >> Right. But don't you think that this kind of use of Unix tools >> must be investigated such that the Unix design choices are taken >> into account while doing so? > >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. 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.