Chris Holmes a écrit :
Idealy we should all follow the
conventions and use jalopy before commiting code. BUT if that does
not happen DO NOT go refomating other peoples code [...snip...]
Though I think we originally left the details of this question up to the
module maintainers. They can choose the specifics of how much to
enforce code formatting on their particular module. Within the general
guideline that geotools has a specific format that we want everyone to
follow. It's just up to them to implement how that happens.
I didn't talked about formatting before, but I'm a little bit confused.
I though that we were suppose to follow the Sun Code Conventions at
http://java.sun.com/docs/codeconv/ but I have the feeling that the code
is formatted differently in regards of whitespaces. For example I see
code like that in many places in Geotools:
myMethod( arg1, arg2 );
for( expr1; expr2; expr3 )
While the Sun convention according
http://java.sun.com/docs/codeconv/html/CodeConventions.doc7.html#475 is:
myMethod(arg1, arg2);
for (expr1; expr2; expr3)
Does it means that our code conventions is something different than the
Sun code convention? I was trying to follow the Sun code convention in
my code.
Martin.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
