On 08/17/2015 06:22 AM, andy pugh wrote: > On 17 August 2015 at 13:15, Kenneth Lerman <ler...@se-ltd.com> wrote: >> The "problem" with defaulting them to the enabled state is that the meaning >> of previously valid programs change. (Of course it is unlikely that someone >> happened to use a variable with an odd name like that -- some might say >> pathological.) We generally like changes to be backwards compatible. Having >> the default as disabled preserves backwards compatibility. > > I see the point, but it also seems wrong to have to "turn on" any > feature that is to be considered "normal" > And I would be prepared to bet several pounds that nobody has ever > used a named parameter in that format by mistake.
I think it's ok to break backwards compatibility at major version changes (such as 2.6 -> 2.7). I'm open to turning this useful(?) feature on by default for 2.7. Thoughts? Comments? -- Sebastian Kuzminsky ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
