As for seeing a class structure, this is what IDE's like Eclipse and IDEA make a moot point. I think if code doesn't follow the Jakarta (or project-specific) conventions then its fair game for reformatting. This is communal code and no one person owns it, this is why conventions exist and we must adhere to them for the sake of the "community". Please.

But, while we are talking about coding conventions, at least please adopt closing if/for/while/etc blocks with curly brackets for one-line blocks. The Struts codebase is littered with non-curly-bracketed one-line blocks and that in and of itself drives me nuts when I'm trying to follow the code. :))

Erik


Cedric Dumoulin wrote:

I said that I don't want to debate on this. I know the reformated code doesn't follow the recomanded Jakarta rules code standard. But another rule is to respect any other well formated standard ;-).
For me, the reformated code is really unreadable: I can't detect the classes and methods structures at a glance, and so it requires me some times to try to figure it out. I thing it is a waste of time ...

Cedric

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to