Coding Standards

1. Each source module will contain at most ten procedures of similar function (as indicated by the module name).  The procedures within a module must be separated by several blank lines.
2. Each procedure will contain a header comment identifying the procedure by name and function.
3. Each procedure will contain at most 100 lines of executable code, not counting comments or declarations.
4. Use variable names which are meaningful.
5. No comment will continue across line boundaries.  Close the comment at the end of a line and open it again on the next line.
6. At most one statement will occur on a line.  If a statement spans several lines, it will be indented in a consistent fashion (to indicate continuation).
7. Blank lines and extra spaces will be used freely to increase readability.  In particular, the assignment operator (=) will always be enclosed in spaces.  Use parentheses for clarity.
8. The use of the GOTO statement is very strongly discouraged.
9. No string constant will be split between two lines.
10. No code may succeed a `{' nor precede a `}' on a line.
11. All programs will be indented in the following manner:
    • Each `}' will be in the same column as the beginning of the text of the line containing the `{' that it closes.
    • In an if-then-else construct, the else will start in the same column as the if.
    • Statements immediately contained within a bracketed pair will all start in the same column, and that column will be indented consistently to the right of the bracketing statement's starting column by two to five spaces.  Note that, of course, the contents between the bracketing statements will have to be indented with respect to the outer indentation.  For example,
      

      	if (x == 5) {
      	     y = 7;
      	     printf("x is five\n");
      	}
      	else {
      	     y = 10;
      	     printf("x is not five\n");
      	}