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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,6bf1c4b845bd2160 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,UTF8 Path: g2news1.google.com!news3.google.com!proxad.net!feeder1-2.proxad.net!usenet-fr.net!gegeweb.org!aioe.org!not-for-mail From: =?utf-8?Q?Yannick_Duch=C3=AAne_=28Hibou57?= =?utf-8?Q?=29?= Newsgroups: comp.lang.ada Subject: Re: What about a glob standard method in Ada.Command_Line ? Date: Wed, 25 Aug 2010 23:32:26 +0200 Organization: Ada @ Home Message-ID: References: <4c6f9837$0$5420$ba4acef3@reader.news.orange.fr> <4c739e76$0$6992$9b4e6d93@newsspool4.arcor-online.net> <152a2z5en4z2o$.xjsuqr7s8yak$.dlg@40tude.net> <4c73e859$0$6991$9b4e6d93@newsspool4.arcor-online.net> <4c73fcf6$0$6992$9b4e6d93@newsspool4.arcor-online.net> <1jxm50y65grlo.sjyb9hm4y1xp$.dlg@40tude.net> <4c743a59$0$6893$9b4e6d93@newsspool2.arcor-online.net> NNTP-Posting-Host: H0Ci3WDhdyTdURnA0sNEyw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: Quoted-Printable X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 User-Agent: Opera Mail/10.61 (Win32) Xref: g2news1.google.com comp.lang.ada:13743 Date: 2010-08-25T23:32:26+02:00 List-Id: Le Wed, 25 Aug 2010 23:05:43 +0200, (see below) = a =C3=A9crit: > tual/understanding_utis/understand_utis_conc/understand_utis_conc.html= #//app > le_ref/doc/uid/TP40001319-CH202-CHDHIJDE> I am quoting the above document: A key advantage of uniform type identifiers over other type identification methods is that they are declared in a conformance hierarchy. A conformance hierarchy is analogous to a class hierarchy= in object-oriented programming. Instead of =E2=80=9Ctype A conforms = to type B,=E2=80=9D you can also think of this as =E2=80=9Call instance= s of type A are also instances of type B.=E2=80=9D This is indeed the most logical way to handle file types. Would be nice = as = a public standard, but would require this to be followed, which is anoth= er = affair (what I do not enjoy with the Windows way, is the too much freque= nt = clashes with file extensions, and as soon as a clash is there, this make= = the given file extension mostly unusable). -- = * 3 lines of concise statements is readable, 10 pages of concise = statements is unreadable ; * 3 lines of verbose statements may looks unuseful, 10 pages of verbose = = statements will never looks too much pedantic