Coding Guidelines

What do we want for the coding outlines/layout? These are open to discussion

Do not use abbreviations

For Java
Use javaDoc comments

Keep properties private - use get and set methods

Like this?
private String something;

public void setSomething(String something)
        this.something = something;
 [tab]  if(this.else)
          [tab] somethingElse();

Package naming - maybe something like ca.gridx1.sp.[package name]

TIP Maybe we should use spaces instead of tabs in our coding standards. When tabs are used, it often defaults to 8 spaces, which often leads to difficult to read code when there is more than 3 or 4 indentation levels. Most modern text editors and/or IDE can do the conversion between tabs and spaces automatically. Usually, I prefer a small number of spaces for indentation, such as 2, as it leads more space for longer (more descriptive) variable, class and method names.

-- AndreCharbonneau - 11 May 2006

-- ChrisUsher - 21 Mar 2006

This topic: HEPrc > Analysis52BaseVM > CodingGuideLines
Topic revision: r5 - 2011-02-08 - fransham
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback