std.getopt suggestion

[Andrei Alexandrescu]

On 10/4/11 3:10 PM, Christophe wrote:
> Andrei Alexandrescu , dans le message (digitalmars.D:146070), a écrit :
>> On 10/4/11 2:39 PM, Andrei Alexandrescu wrote:
>>> On 10/4/11 12:05 PM, Christophe wrote:
>>>> Andrej Mitrovic , dans le message (digitalmars.D:146060), a écrit :
>>>>> I'm don't often use getopt just for the fact that I can't use
>>>>> single-dash arguments like '-release'. DMD uses this syntax, and so to
>>>>> other tools. It's not a big deal thanks to D's fantastic
>>>>> string-manipulation abilities, so I just roll my own. All I need is a
>>>>> switch(args) statement.
>>>>
>>>> I don't use getopt often either. That does not prevent me to wish getopt
>>>> could become adequate to my needs...
>>>
>>> It already is because your needs are the empty set.
>>>
>>> Andrei
>>
>> On second thought what you said suggests your needs set may be nonempty,
>> but said needs are not fulfilled by the current std.getopt.
>>
>> What exactly in std.getopt does not fulfill your needs? Would assembling
>> the three variables into a structure help?
>
>
> No, it wouldn't.

Aha!

> The main reason why I don't want to use getopt is because the syntax "-o
> output" (short-option, space, argument), and that is the main thing
> I want to do. I think I posted about this in the thread.

This is a sensible thing to ask for.

> Enabling single-dash long option would be nice too.

Hm, that's a bit unusual (albeit dmd does use it). The problem is this 
feature interacts badly with bundling of single-letter arguments, i.e. 
does -in mean --in or -i -n?

> The fact that it uses global parameters just doesn't help.

It doesn't hurt one soul. It's a non-problem.


Andrei