Command line parsing

[Andrei Alexandrescu via Digitalmars-d]

On 5/14/16 10:29 AM, Russel Winder via Digitalmars-d wrote:
> On Sat, 2016-05-14 at 16:17 +0300, Andrei Alexandrescu via Digitalmars-
> d wrote:
> […]
>
>> I showed a fellow programmer std.getopt. We were both on laptops. He
>> wanted to show me how good Python's argparse is and how D should
>> copy
>> it. By the end of the chat it was obvious argparse was much more
>> verbose
>> and less pleasant to use than getopt. Like you have to create an
>> object
>> (?!?!) to parse the command line and many other lines of nonsense.
>
> "verbose", "less pleasant" and "nonsense" are hardly the right terms
> unless the intention is to try to convince us using advocacy research.

Now that I've read your "getopt is a 1970s C solution..." comment I 
realize this might be a simple misunderstanding related to the fact 
you've never looked at D's std.getopt. It has nothing to do with C's 
getopt. The closest ancestor is Perl's 
http://perldoc.perl.org/Getopt/Long.html, but in D it's a lot better 
because of strong typing. Pray please take a look and sorry for taking 
your confusion for a semantic grenade. -- Andrei