On Sat, Mar 24, 2018 at 05:24:28PM -0400, Andrei Alexandrescu via Digitalmars-d wrote: > On 3/24/18 12:59 PM, H. S. Teoh wrote: > > On Sat, Mar 24, 2018 at 12:11:18PM -0400, Andrei Alexandrescu via > > Digitalmars-d wrote: > > [...] > > > Anyhow. Right now the order of processing is the same as the > > > lexical order in which flags are passed to getopt. There may be > > > use cases for which that's the more desirable way to go about > > > things, so if you author a PR to change the order you'd need to > > > build an argument on why command-line order is better. FWIW the > > > traditional POSIX doctrine makes behavior of flags independent of > > > their order, which would imply the current choice is more natural. > > > > So what about making this configurable? > > That'd be great. I'm thinking something like an option > std.getopt.config.commandLineOrder. Must be first option specified > right after arguments. Sounds good?
Great! Not so sure how easy it is to implement while supporting everything else, though, given the current structure of the code. T -- Time flies like an arrow. Fruit flies like a banana.
