Difference between revisions of "OOP344 20131 - See Plus Plus"
Erik Dokic (talk | contribs) m (moved 20131 OOP344-SeePlusPlus to OOP344 20131 - See Plus Plus: Conformity to specs.) |
Erik Dokic (talk | contribs) (→Team Members) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 11: | Line 11: | ||
== Coding Style == | == Coding Style == | ||
| − | 1.Naming | + | 1. Naming |
| − | * Names representing types must be in mixed case starting with upper case (example: SavingAccount) | + | * Names representing types must be in mixed case starting with upper case (example: SavingAccount). |
| − | * Variable names must be in mixed case starting with lower case | + | * 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 | + | 2. Indentation and block layout examples |
while (!done) { | while (!done) { | ||
doSomething(); | doSomething(); | ||
| Line 22: | Line 23: | ||
} | } | ||
| + | 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 == | == Team Members == | ||
| − | [mailto:rbcruz@myseneca.ca;xdeng7@myseneca.ca;edokic@myseneca.ca;amendes@myseneca.ca;?subject= | + | [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 15:27, 15 February 2013
OOP344 | Weekly Schedule | Student List | Teams | Project | Student Resources
Contents
See Plus Plus (Team 3)
Project Marking Percentage
Github Repository
- git@github.com:Seneca-OOP344/3-SeePP.git
- https://github.com/Seneca-OOP344/3-SeePP.git
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) {
doSomething();
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
| 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 |
