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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,21def7b4562d91bf X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,CP1252 Received: by 10.224.72.199 with SMTP id n7mr4490331qaj.5.1355588419240; Sat, 15 Dec 2012 08:20:19 -0800 (PST) Received: by 10.49.128.166 with SMTP id np6mr1705166qeb.31.1355588419225; Sat, 15 Dec 2012 08:20:19 -0800 (PST) Path: k2ni7qap.0!nntp.google.com!fc2no925987qab.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sat, 15 Dec 2012 08:20:19 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=93.37.82.182; posting-account=9fwclgkAAAD6oQ5usUYhee1l39geVY99 NNTP-Posting-Host: 93.37.82.182 References: <0160c8ce-1e7c-4e2c-9641-c76502adadd9@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <9e1a279f-5dc0-47a8-8196-05de1f95e9da@googlegroups.com> Subject: Re: GCLP (Generic Command Line Parser) 1.0.0 released From: mockturtle Injection-Date: Sat, 15 Dec 2012 16:20:19 +0000 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Date: 2012-12-15T08:20:19-08:00 List-Id: On Saturday, December 15, 2012 12:33:41 AM UTC+1, Hibou57 (Yannick Duch=EAn= e) wrote: > Le Fri, 14 Dec 2012 22:17:17 +0100, mockturtle a = =20 >=20 > =E9crit: >=20 > > fictional.exe input=3Dfoo.txt output=3Dbar.xml >=20 > If that's a real life example,=20 No, it is not a real life example. I just added .exe to emphasize that "fi= ctional" was a command. > then it does not follow the standard on =20 >=20 > Windows platform (as that's an *.exe), which is to use a slash prefix for= =20 >=20 > parameters. Do you mean something like=20 fictional.exe /input=3Dfoo.txt /output=3Dbar.xml Well, you could do this as well, by setting the parameter names to "/input"= and "/output". By the way, the real "translation" of this under Linux wou= ld be fictional.exe --input=3Dfoo.txt --output=3Dbar.xml and you can do this as well, by using "--input" and "--output" as parameter= names. >=20 >=20 >=20 > One nice feature of a command line parser I believe, is to allow to be = =20 >=20 > close to the platform standard. There's already too much inconsistencies = =20 >=20 > with too many applications not following any common standard. In return, = =20 >=20 > this make the command line interaction more intuitive and straight away. I agree that this differentiates itself from the usual syntax. I choose th= is approach (and wrote this package) once that I needed to write a program = with a fairly complex syntax and with many possible variations. So, I deci= ded for this approach that, you could say, have no (positional) parameters,= but only options. In this case, the "--", "-" or "/" necessary to mark an= option became redundant. Nothing prevents you to put that back in the op= tion name, if you desire. >=20 >=20 >=20 > That's just a personal opinion. >=20 >=20 Thank you for your interest. Riccardo >=20 >=20 >=20 > --=20 >=20 > =93Syntactic sugar causes cancer of the semi-colons.=94 [1] >=20 > =93Structured Programming supports the law of the excluded muddle.=94 [1] >=20 > [1]: Epigrams on Programming =97 Alan J. =97 P. Yale University