Difference between revisions of "The Sixth Core 20123 - OOP344"

From CDOT Wiki
Jump to: navigation, search
(Coding Rules)
Line 51: Line 51:
 
*:  
 
*:  
 
== Coding Rules ==
 
== Coding Rules ==
* Comment shortly and properly, specially at the end of long scopes;
+
* Use Safegaurd for header files with the format of _OOP_FILENAME_H_
* Data members in any classes start with underscore(_);
+
* Data members in any classes start with underscore(_)
 
* Use Capital letter for the second word of variables with compound words
 
* Use Capital letter for the second word of variables with compound words
* Use meaningfully variable name;
+
* Use meaningfully variable names
* Use Safegaurd method
+
* Use 3 spaces for indentation
 +
* Use only SPACE BAR for indentation (do not use Tab)
 +
* Use curly-braces for all kinds of loops, if statement, switch, etc.
 +
* Comment shortly and properly, specially at the end of long scopes
  
 
== meetings ==
 
== meetings ==

Revision as of 19:23, 23 October 2012


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

The Sixth Core (XIII)

Project Marking Percentage

  • due immediately

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

Repository

  • repo Github id:

Team Members

Team Name (The Sixth Core)
First Name Last Name Section Seneca Id wiki id IRC nick Blog URL
Amir Mohammad Mobasseri B ammobasseri ammobasseri ammobasseri Amir's Blog
Saeid Ahankoub B sahankoub Saeid Ahankoub sahankoub C++ Blog
Prateek Chadha B prateek Prateek Chadha aviat0r prateek chadha
Ahmad Al Dallal B aaldallal Ahmad Al Dallal icanada BlogName
Ali Al Dallal B aaldallal1 Ali Al Dallal alihuta2002 Ali's Blog

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:

Issue description and/or number (2)

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

Coding Rules

  • Use Safegaurd for header files with the format of _OOP_FILENAME_H_
  • Data members in any classes start with underscore(_)
  • Use Capital letter for the second word of variables with compound words
  • Use meaningfully variable names
  • Use 3 spaces for indentation
  • Use only SPACE BAR for indentation (do not use Tab)
  • Use curly-braces for all kinds of loops, if statement, switch, etc.
  • Comment shortly and properly, specially at the end of long scopes

meetings

  • latest will be on top
  1. topic and date1
  2. topic and date2

discussions