Difference between revisions of "Hadouken"

From CDOT Wiki
Jump to: navigation, search
(Hadouken (Team XI) 20123 - OOP344)
(Coding Rules)
Line 38: Line 38:
 
*:
 
*:
 
== Coding Rules ==
 
== Coding Rules ==
 +
* Curly brackets for code blocks start after the condition and end on an empty line.
 +
if(condition){ // Comment on what it does
 +
code
 +
code
 +
} // 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
 +
 
== Meetings ==
 
== Meetings ==
 
* latest will be on top
 
* latest will be on top

Revision as of 14:03, 1 November 2012


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%

Repository

  • 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
code
code
} // 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

Meetings

  • latest will be on top
  1. IRC meeting logs

Discussions