Here are a few Java Style Manuals for reference:
__I propose that we use Sun's Code Conventions as our first draft and review each section for additions, deletions or revisions that we might want to incorporate.__
We should conduct these discussions on the MailingLists , now that we have our own.
--BillRehm
The sections:
- Intro - no discussion needed.
- CodingStandardFileNames ( FileNames )
- CodingStandardFileOrganization ( FileOrganization )
- CodingStandardIndentation
- Pleases don't add more until we've reached consensus on the ones currently under discussion.
I've been thinking about CodingStyle & CodingConventions lately. What keeps popping into my head are the comments made by PeterMerel and MichaelFried on the CodingConventionsBracePlacement page. Namely, that brace placement could be dealt with by a PrettyPrinter. It dawned on me that most CodingConventions could be handled by a PrettyPrinter and we should just build that tool & let users view the code the way they liked best. Maybe we should start going through these style guides and throw each rule into one of three piles:
- we need to make that rule part of our CodingStyle
- that rule should be a PrettyPrinter configuration
- that rule is already enforce by Java
Then we'll just design & build the PrettyPrinter.
--BillRehm
I agree with BillRehm,
There is not need to be to strict with elements such as braces or indentation... there are all kinds of formatters availible. Let each developer use the style he/she likes.
The one i use in conjunction with Kawa, is astyle...
-- BrillPappin 16-JAN-1999
|
Content of these pages are owned and copyrighted by the poster.
|
|
Hosted by:
|
|