Re: Why so many imports instead of java.io.* ?
On 8/20/2012 9:09 AM, Timothy Madden wrote:
....
I don't appreciate coding conventions either. For once, they are
mischievously named "conventions", "style" or "guidelines", but if you
don't follow them, you can't work in project ... which makes them hard
rules, not conventions.
I do think a project should have rules, not conventions. I don't care
much what they are, as long as visible indent reflects logical nesting.
When I'm modifying existing code one of my objectives is to fit my
changes in smoothly, so that they don't break the thread for someone
reading the code. That means, among other things, following the same
style as the surrounding code.
If code within a project is formatted according to the preferences of
the programmer who created each module, I would have to either manually
format, with the risk of indent mistakes, or change the IDE to suit each
module.
If the project has a set of rules defined from the start, I can just set
my IDE project style settings appropriately and edit any module in the
project.
Gene goes a stage further than I would personally, and maintains style
consistency between languages, which results in an unusual style for his
Java code.
Patricia