Style Guide for CS 139

• Variable and method names should begin with a small letter.  subTotal
• Variable names should be noun phrases (studentName or subTotal)
• Method names should be verbs or verb phrases (print_line or addColumn)
• Class names should begin with a capital letter and use title case. HelloWorld.  
• Constant names should be all caps with an underscore separator. PI, INTEREST_RATE.

• All variables and constants should be declared at the top of the method or class in which they are used.
• Each declaration should be on its own line.  Comment to the right if the name is not self explanatory.
• It is permissible to initialize a variable as you are declaring it.
• Group declarations by type and put them in alphabetical order by type and within type by name.
• Variables should be declared at the top of the method or class and instantiated in the body of the code when needed.
• Constants should be declared and initialized at the top of the method or class.

• Sub sections of code should be indented a consistent 3 spaces for readability.  
• Blocks of code surrounded by curly braces should have the curly braces line up vertically and the open brace should line up directly beneath the first letter of the header for that block.
• An alternate format for the block is to have the open brace on the same line as the header and the closing brace to line up with the first letter of the header.
• Statements which are too long for the line should be indented 1 space for the 2nd and subsequent lines.

• Binary operators should be separated from their operands by a single space on either side.  Unary operators should not have a space.
• It is okay to condense the operand and operator in a for loop header.
• Ex: sum = myGrade + yourGrade;  myGrade++;
• An exception is the dot (.) operator which does not have space surrounding it. Ex: System.out.println();

• One line of white space should follow the declaration of variables.
• Use white space to separate segments of code.
• In a class declaration, constructors should precede all other methods, then the methods should be in order by visibility modifier then alphabetically within the same modifier..
• Lines should be kept to a short length (<80).  You should be able to see the full line in your editor and in the submit system.

• Must come before the code that they are describing or if brief on the same line.
• In-line comments (//) should describe major structures or steps within a method.
• Block comments(/* */) should describe each class and method.
• Should use normal English spelling and grammar.  Phrases are okay.

Header - every source file must contain the following in its header. The * on each line is optional, but you must clearly delineate the class header from code.
/***************************************************************************
* Overall description of the class goes here
*
* @author Your name goes here
* @version Vn - date
*  Description of the assignment (ex: Lab1, PA1 - Mile conversion)
***************************************************************************/

Programming Assignments - Every programming assignment must contain the following statement or must cite any sources used (such as a TA).
/***************************************************************************
* References and Acknowledgements: I received no outside help with this
* programming assignment
*
 ***************************************************************************/
OR
/***************************************************************************
* References and Acknowledgements: TA Glenn helped me with the foo method.
*
 ***************************************************************************/

Methods - All methods must contain a header which contains the following if applicable.  Make sure that you do not give
an @param or @return tag for methods that take no parameters or which do not return a value. The * on each line is optional, but you must clearly delineate the method documentation from code.
/***************************************************************************
* Overall description of the method goes here
*
* @param paramterName Describe each input parameter, must have one @param line for each
* @return Describe the value that this method returns.
***************************************************************************/

Miscellaneous

• Methods should have a single return statement if it is a value returning method.
• You may not use the break statement except for within the switch statement.
• All class variables should be private unless there is a documented reason for not doing so.
• All class constants should be public unless there is a documented reason for not doing so.
• All visibility modifiers should be explicitly stated.