|
From: Andreas L. <no...@sb...> - 2001-10-22 11:33:32
|
On Mon, 2001-10-22 at 11:09, Eric Bezault wrote: > Sven Ehrke wrote: > > > > I could change this of course if most of you would prefer the --define syntax. > > Just let me know. > > Can't they both be supported: long or short option name? Yep, short options are also allowed. But for short options the '=' is disallowed. Some apps take accept the value just with a space, but personaly I think it is cleaner to allow only long options a value and let short options server for boolean flags. Dunno what the specs say here exactly. IMO should every short option have a long option pendant, if only for self documentation purposes. Whereas long options need not have short option pendants. If I see a usage listing like: -v, --verbose ... some explanation I don't even need to look at the right hand for an explanation. The long option tells me all I need, plus it tells me what shorthand I can use. If I only see '-v' without the explanation, I could only guess what it means (version, verbose, volatile, ... :) Andreas |