> I assume the braces for while/for/if/try/catch/finally/etc. will be the > same > as for classes/methods... > Aslak
No I was just talking about class/methods, because I know many ppl love braces in end of lines for if/else/... but class/method maybe not. I'll assign you minister of coding conventions if you vote +1, so let me know if you want to change your vote ;-) Btw something missing (a bloody one!) is indent count. In Mathias's proposal it's 4. I think 3 is better. So: - Indent count 2- 3- Ara: +1 4- And no tabs, all spaces please. PS: It's at least a good exercise to practice what we've been preaching just a few days ago regarding voting/team-work. Ara. > Coding convention: > 1. Brace in new lines for class > Ara: +1 > Mathias: -1 > David: +1 > Konstantin: -1 > Aslak: -1 > > 2. Brace in new lines for methods > Ara: +1 > Mathias: -1 > David: +1 > Konstantin: -1 > Aslak: -1 > > 3: No @todo-javadoc stubs > Ara: +1 > Mathias: +1 > David: +0 > Konstantin: -1 > Aslak: +1 > > 4. Spaces before/after parenthesis > Ara: +1 > Mathias: -1 > David: -1 > Konstantin: +1 > Aslak: +1 > > Checkstyle: > 1. Use checkstyle out of the box (sun's convention) > Mathias: +1 > > 2. Use checkstyle with some modifications > Ara: +1 > David: +1 > Konstantin: + 1 > Aslak: +1 > > 3. don't use > > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We supply > the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] > _______________________________________________ > Xdoclet-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
