T
Tim Kuehn
Guest
Now we have 3 Alex answers! 
With respect to features not changing once they're released - there is precedent for changing or reverting feature behavior that caused the user base an issue. With respect to what to do now - I'd be fine with having the default behavior be error-only **if** you added a sub-option to enable changing the compiler response to a warning. Error as default will encourage good code writing in the future. Warning as an option will enable large-code-base shops to progressively work through their code base and do a strict compile to an error on files that are clean so they stay that way, and a strict compile to a warning on files that still need work.
Continue reading...
With respect to features not changing once they're released - there is precedent for changing or reverting feature behavior that caused the user base an issue. With respect to what to do now - I'd be fine with having the default behavior be error-only **if** you added a sub-option to enable changing the compiler response to a warning. Error as default will encourage good code writing in the future. Warning as an option will enable large-code-base shops to progressively work through their code base and do a strict compile to an error on files that are clean so they stay that way, and a strict compile to a warning on files that still need work.Continue reading...