Difference between revisions of "The Sixth Core 20123 - OOP344"
(→Team Members) |
Ammobasseri (talk | contribs) (→Coding Rules) |
||
| Line 51: | Line 51: | ||
*: | *: | ||
== Coding Rules == | == Coding Rules == | ||
| − | * Use Safegaurd for header files with the format of | + | * Use Safegaurd for header files with the format of '''_XIII_FILENAME_H_''' |
| − | * Data members in any classes start with underscore(_) | + | * Data members in any classes start with underscore(_), for example '''_data''' |
| − | * Use Capital letter for the second (third, forth, ...) word of variables with compound words | + | * Use '''Capital letter''' for the second (third, forth, ...) word of variables with compound words |
* Use meaningfully variable names | * Use meaningfully variable names | ||
| − | * Use | + | * Use '''2 spaces''' for indentation |
| − | * Use only SPACE BAR for indentation (do not use Tab) | + | * Use only '''SPACE BAR''' for indentation (do not use Tab) |
| − | * Use curly-braces for all kinds of loops, if | + | * Use curly-braces for all kinds of '''loops, if statements, switch, etc.''' For example, |
| − | * Comment shortly and properly, specially at the end of long scopes | + | if (condition){ |
| + | code; | ||
| + | } // end if | ||
| + | * '''Comment''' shortly and properly, specially at the end of long scopes | ||
| + | * You can use extra spaces to align statements or blank line between parts of the code that you are going to put comment | ||
== meetings == | == meetings == | ||
Revision as of 14:21, 4 November 2012
OOP344 | Weekly Schedule | Student List | Teams | Project | Student Resources
Contents
The Sixth Core (XIII)
Project Marking Percentage
- due immediately
Group work: 35% (25 <= xx <= 50) Individual work: 65% + (50 <= xx <= 75) ------------------------- Total 100%
Repository
- repo Github id: XIII-SixCor
Team Members
| 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 |
| Rocco | Pietrangelo | A | rmpietrangelo | WikiID | IrcNick | oop344-seneca |
| [[User: | ]] | [1] | [ ] |
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 _XIII_FILENAME_H_
- Data members in any classes start with underscore(_), for example _data
- Use Capital letter for the second (third, forth, ...) word of variables with compound words
- Use meaningfully variable names
- Use 2 spaces for indentation
- Use only SPACE BAR for indentation (do not use Tab)
- Use curly-braces for all kinds of loops, if statements, switch, etc. For example,
if (condition){
code;
} // end if
- Comment shortly and properly, specially at the end of long scopes
- You can use extra spaces to align statements or blank line between parts of the code that you are going to put comment
meetings
- latest will be on top
