1
edit
Changes
m
→Updated page to include coding style of the team
= Coding Style = The Coding Rangers had their first somewhat informal meeting on Jan. 21 to determine a uniform coding style. They came up with the following: <ul> <li>Comment as much as you can using /* ... */.</li> <li>Change to newline once you reach <b>column 80</b>. Nothing to be typed beyond column 80!</li> <li>When naming variables, <ul> <li>use single letters (like i, j, a, or v) for counters only. </li> <li>assign the name that best describes what a variable is used for (but please don't make it too long)</li> <li>separate words with caps. <br />Eg. no<b>O</b>f<b>O</b>rders, not no<b>o</b>f<b>o</b>rders </ul> </li> <li>Tabbing/Spacing: As most of us have decided to date use vi, we have determined that <b>TABBING 2 SPACES</b> will be the norm. <li>Only <code>main ()</code> will start at column 1. Tab everything else two spaces over</li> <li>When using operators, make sure to have a space between the operands and the operator for readability. <br/>Eg. <code>i = 0;</code>, not <code>i=0;</code></li> <li>For keywords such as while, for, if, else, put a space after the keyword and the expression following it. <br/> Eg. if <code>(x==0)</code> is correct, not begun any sort of coding<code>if(x==0)</code></li> <li>When using brackets, put the opening bracket on the same line as the function or expression that opens it. <br/>Eg. <br/>int setSafeEmptyState { <br/>... <br/>} is correct <br/>int setSafeEmptyState <br/>{ <br/>... <br/>} is incorrect </li></ul>
