Re: [PATCH 1/6] gitopt: a new command-line option parser for git

From: Timo Hirvonen <tihirvon@gmail.com>
Date: May 9, 2006, 09:08 UTC
Message-ID: <20060509120809.4d9494b9.tihirvon@gmail.com>
In-Reply-To: <11471512103526-git-send-email-normalperson@yhbt.net>

Eric Wong <normalperson@yhbt.net> wrote:

>  * unbundling of short options: -uC20n20z => -u -C20 -n20 -z

Does anyone ever use this? I think this makes sense only for flags that don't have parameters but that would create an ugly special case. Is it too hard to type "-u -C=20 -n=20 -z"?

>  * optional argument handling (-C<num>, -M<num>)
>    -C <num> (with a space between them) has not changed,
>    however, <num> can be a sha1, or a path

IMO optional arguments are usually bad idea.

    -C 2 (is "2" argument?)
    -C2  (-C=2 or -C -2?)

Better to make it obvious there's an argument

    -C=2

or not support optional arguments at all and "-C 2" becomes unambiguous.

-- 
http://onion.dynserv.net/~timo/