> Regarding coding conventions, I almost agree with you expect on the
> following points :
> * When I commit some code, I like to follow the existing coding conventions
> so that it is easier to read and understand the code. You can usually do
> this by following the existing conventions. However, by looking at the file
> I have found several conflicting conventions so I am not sure which to use
I'd have thought that people should follow the coding convention of a
file, but create new files in their own convention.
> * For debugging, it is very important to have conventions like the one I
> have proposed otherwise it makes reading log files very hard or impossible
> (like logging entry/exits of methods, ...)
I disagree with this part of your proposal. I don't think debugging should
ever go into a log file. Logging goes to a log file, debugging goes to
System.err and never gets committed into cvs.
> * I do *really* care if you use tabs instead of spaces because it makes the
> code undreadable and is really annoying.
Agreed.
As far as coding standards go, there is one, it's on Sun's website and it
accounts for most issues. Probably the biggest issue that it doesn't cover
is where spaces/tabs/newlines go. Lots of IDEs seem to reformat source to
a user's preferred settings, which is nice for them but nasty for a
project as CVS will be overworked and unable to provide good output.
Equally, CVS could be set so that it reformats all code before
committing(?)
I'm sure it's a target for flame, but rather than concentrating on things
like formatting of code, I think focus should be on conventions like,
never importing wildcards. This is far more painful from my view than how
indented a line is etc.
Bay
