Difference between revisions of "Team Mighty Morphin Coding Rangers - OOP344"

From CDOT Wiki
Jump to: navigation, search
m (Coding Style - changes spacing from 2 to 4, added empty line after variable declaration)
(added in member list)
Line 64: Line 64:
  
 
</ul>
 
</ul>
 +
 +
= Member list =
 +
 +
{| class="wikitable sortable" border="1"  cellpadding="5"
 +
 +
 +
! Last Name  !! Name !! Seneca Username !! Section !! Blog Url !! IRC Nick !! SVN ID  !! My Contributions !! Role
 +
|-
 +
 +
| Cheung|| Christopher|| [mailto:cgcheung@learn.senecac.on.ca?subject=OOP344 cgcheung] || B || http://rocketpants.blog.ca/ || Rocketpants || n/a || [[Special:Contributions/cgcheung | Contributions]] || Team Contact
 +
|-
 +
 +
| Huang|| Dachuan|| [mailto:dhuang18@learn.senecac.on.ca?subject=OOP344 dhuang] || B || http://hdc23.wordpress.com/  ||  Da_Truth || n/a  || [[Special: Contributions/dhuang18 | Contributions]] || Team Contact
 +
|-
 +
 +
| John-Sandy|| Anastasia|| [mailto:ajohn-sandy@learn.senecac.on.ca?subject=OOP344 ajohn-sandy] || B || http://anastasiasaurus.blogspot.com  || annieJS || n/a  || [[Special:Contributions/ajohn-sandy| Contributions]] || Team Contact
 +
|-
 +
 +
| Oberes|| Donna|| [mailto:daoberes@learn.senecac.on.ca?subject=OOP344 daoberes] || B || [http://donna-oberes.blogspot.com Blog] ||  Donna_Oberes || n/a  || [[Special:Contributions/daoberes| Contributions]] || Team Contact
 +
|-
 +
 +
| Wang|| Shengwei|| [mailto:swang94@learn.senecac.on.ca?subject=OOP344 swang94] || A || http://shengwei-seneca.blogspot.com/ || Shengwei || n/a  || [[Special:Contributions/swang94 | Contributions]] || Team Contact
 +
|-
 +
| Wang|| Cong|| [mailto:Cwang84@learn.senecac.on.ca?subject=OOP344 Cwang84] || A || http://wangcong422.blogspot.com/ || cwang84 || n/a  || [[Special:Contributions/cwang84 | Contributions]] || Team Contact
 +
 +
|-
 +
| Xue|| Yong|| [mailto:yxue11@learn.senecac.on.ca?subject=OOP344 yxue11] || A || http://yxue11.blogspot.com/ || yxue11 || n/a  || [[Special:Contributions/yxue11| Contributions]] || Team Contact
 +
|-
 +
 +
| Chau|| Sunny|| [mailto:schau5@learn.senecac.on.ca?subject=OOP344 schau5]|| B || [http://s2000c.blogspot.com/ Blog] || ScsC|| TBA  || [[Special:Contributions/schau5| Contributions]] || Team Contact
 +
 +
|}

Revision as of 12:10, 25 January 2010

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:

  • Comment as much as you can using /* ... */.
    • At the top of every file, include your name, the filename, and the purpose of the file.
    • Comment on what a function is supposed to do before the function definition.
  • Change to newline once you reach column 80. Nothing to be typed beyond column 80!
  • When naming variables,
    • use single letters (like i, j, a, or v) for counters only;
    • assign the variable a name that best describes what it is used for (but please don't make it too long);
    • and separate words with caps.
      Eg. noOfOrders, not nooforders
  • When naming a function, name it according to what it is supposed to do.
    Eg. void updateDelivery, int setInitialValue, not void Deliveries, int InitialValues
  • Class names must begin with a capital letter
  • Tab/space four (4) spaces for every block of code. For example:
  •  main () { 

    int x, y;

    for (x = 0, y = 10; x < 10 && y > 0; x++, y++) {
    printf("x is %d, y is %d\n", x, y);
    printf("The sum of x and y is %d\n", x + y);
    if (x == 5)
    printf("We've reached the halfway point!\n"); }

    printf("Hello, world!");
    }

  • Only main () will start at column 1. Tab every block of code four spaces over.
  • Include an empty line after the declaration of variables (see above example).
  • When using operators, make sure to have a space between the operands and the operator for readability.
    Eg. i = 0;, not i=0;
  • For keywords such as while, for, if, else, put a space after the keyword and the expression following it.
    Eg. if (x == 0) is correct; if(x == 0) is incorrect
  • When using brackets, put the opening bracket on the same line as the function or expression that opens it.
    Eg. CORRECT:
    int setSafeEmptyState {
    ...
    }

    INCORRECT:
    int setSafeEmptyState
    {
    ...
    }

Member list

Last Name Name Seneca Username Section Blog Url IRC Nick SVN ID My Contributions Role
Cheung Christopher cgcheung B http://rocketpants.blog.ca/ Rocketpants n/a Contributions Team Contact
Huang Dachuan dhuang B http://hdc23.wordpress.com/ Da_Truth n/a Contributions Team Contact
John-Sandy Anastasia ajohn-sandy B http://anastasiasaurus.blogspot.com annieJS n/a Contributions Team Contact
Oberes Donna daoberes B Blog Donna_Oberes n/a Contributions Team Contact
Wang Shengwei swang94 A http://shengwei-seneca.blogspot.com/ Shengwei n/a Contributions Team Contact
Wang Cong Cwang84 A http://wangcong422.blogspot.com/ cwang84 n/a Contributions Team Contact
Xue Yong yxue11 A http://yxue11.blogspot.com/ yxue11 n/a Contributions Team Contact
Chau Sunny schau5 B Blog ScsC TBA Contributions Team Contact