From CDOT Wiki
Revision as of 17:45, 4 November 2012 by Kenneth Stewart Cromarty (talk | contribs) (Coding Rules: -Added variables, classes and defines)
Jump to: navigation, search

OOP344 | Weekly Schedule | Student List | Teams | Project | Student Resources

Hadouken (Team XI) 20123 - OOP344

Project Marking Percentage

Group work:      XX%        (25 <= xx <= 50)
Individual work: XX% +      (50 <= xx <= 75) 
Total           100%


  • repo Github id:

Team Members

OOP344 - Team Hadouken
First Name Last Name Section Seneca Id wiki id IRC nick GITHUB ID Blog URL
Andre Mendes A amendes Andre Mendes AndreM andrehsmendes Object Oriented Programming
Kajanthan Tharmabalan A ktharmabalan Kajanthan Tharmabalan C0d3z Kajan- Research C++
Kenneth Cromarty A kscromarty Kenneth Stewart Cromarty kscromarty mrkennc Kenn C.PGM

Issues and Status

Issue description and/or number (1)

  • Assigned to: FULLNAME
  • Code review by: FULLNAME
  • Status:
    (being developed/pull request/being reviewed/pushed to master)
  • comments:

Coding Rules

  • Curly brackets for code blocks start after the condition and end on an empty line.
if(condition){ // Comment on what it does
} // state the end of code block
  • use 2 spaces to indent
  • do not leave any empty lines, if necessary leave a comment on the newline to separate content

  • If variable or class has a measurable value, the units will be added to the end for the var name.
  • Variables will be completely in lower case and declared separately on a new line.
    • Pointers will have the asterisk near the type when casting and near the variable name when not.
  • Classes will begin each words with an uppercase character followed by lowercase characters.


  • Constants and/or variable defines will be all uppercase separated by underscores
  • Types will be casted in lowercase

#define MAX_LENGTH 5
const CAR_TONNES 2
int x;
int* y;
*y = x;
int weightlbs;


  • latest will be on top
  1. IRC meeting logs