Difference between revisions of "OOP344 20131 - See Plus Plus"

From CDOT Wiki
Jump to: navigation, search
(Coding Style)
(Team Members)
Line 34: Line 34:
== Team Members ==
== Team Members ==
[mailto:rbcruz@myseneca.ca;xdeng7@myseneca.ca;edokic@myseneca.ca;amendes@myseneca.ca;?subject=oop344 Email to all members]
[mailto:rbcruz@myseneca.ca;xdeng7@myseneca.ca;edokic@myseneca.ca;amendes@myseneca.ca;?subject=OOP344 Email to all members]
{| class="wikitable sortable" border="1" cellpadding="5"
{| class="wikitable sortable" border="1" cellpadding="5"

Latest revision as of 16:27, 15 February 2013

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

See Plus Plus (Team 3)

Project Marking Percentage

Github Repository

Coding Style

1. Naming

  • Names representing types must be in mixed case starting with upper case (example: SavingAccount).
  • Method names must be in mixed case starting with lower case (example: savingAccount()).
  • Variable names must be in mixed case starting with lower case (example: savingAccount).

2. Indentation and block layout examples

   while (!done) {
       done = moreToDo();
   int i;
   for (i = 0; i < size; i++) {
       cout << data[i] << endl;

3. Empty lines

  • Always leave two empty lines between methods.
  • Normally there are not empty lines in between statements. A maximum of one empty line is permitted to separate logically distinct parts within a single method.

Team Members

Email to all members

First Name Last Name Team Name Section Seneca Id wiki id IRC nick GITHUB ID Blog URL
Xinggui Deng See Plus Plus A xdeng7 Xinggui Deng xgd GaryDeng Deng's Blog
Erik Dokic See Plus Plus B edokic Erik Dokic edokic edokic OOP344 by ED
Ramon Cruz See Plus Plus B rbcruz Ramon Ben Christoffer Cruz ramonCC chrisRC Ramon's Code Blog
Andre Mendes See Plus Plus B amendes Andre Mendes amendes andrehsmendes Object Oriented Programming

Status and Issues


Meet ups