std.getopt suggestion

[Nick Sabalausky]

"Jonathan M Davis" <jmdavisProg at gmx.com> wrote in message 
news:mailman.290.1317291489.26225.digitalmars-d at puremagic.com...
>
> 5. Assuming that we were creating std.getopt from scratch, there would be
> _zero_ benefit in having any of its configuration options be at the module
> level. There is a definite argument for leaving them there given that 
> moving
> them could break code (though honestly, it wouldn't surprise me if no one 
> in
> the history of D has ever written a program that changed any of those
> variables from their defaults given how standard they are and how little 
> gain
> there normally is in changing them),

And that would be a trivial thing to fix anyway. It's not as if it would 
give the same code different semantics.

> but from the perspective of design, I
> don't see any reason why it would ever be better to have the variables be 
> at
> module scope. On the contrary, it goes against what is generally 
> considered
> good design.
>