>> Of course, but automated changes are not guaranteed error-free. I never had an error with Eclipse (use that since 2002 or so).
>> And it's easy to overlook some other change that was accidentally >> committed at the same time. As with every change. Actually with this argument we should stop developing software. You always can commit a change by accident. >> >> If the code is currently self consistent, why change it? Because: Standards rule. IMHO all open source software should follow the programming language standards. Not only oop safes extensibility, also readability does. > > Self consistency is great. People who write the code should have the > most say and I'm not participating here so I'll accept this > community's choice. That said, it would be really nice to have more > consistency within commons itself. That might be a pipe dream but > there you have it :) A big +1 Gary. When no other committers shout, I will stick with Simone said. But in the end I would be glad to have this task done too. Standards > Personal taste Cheers > > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > -- http://www.grobmeier.de --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
