Difference between revisions of "Team U - OOP344 20133"

From CDOT Wiki
Jump to: navigation, search
(→‎Status)
(→‎Coding Style and Standards)
Line 22: Line 22:
  
 
== Coding Style and Standards ==
 
== Coding Style and Standards ==
−
* No Tab Character allowed. (replace tabs with spaces)
+
* No Tab Character allowed. (replace tabs with 4 spaces)
 
* Each object must have its own type:
 
* Each object must have its own type:
 +
* Open { in the same line
 +
* Close } in the next line
 +
* Start else in the next line
 +
* 2 line break for new function
 +
* Declare variable type only in prototyping
 +
* Using namespace cio
 +
* Variables rules
 +
** start with flag p_, l_ (parameter, local)
 +
** class variable start with _
 +
** start with lower character
 +
** use upper character from first letter of each word (from second word)
 +
** remove vowel in a variable
 +
** no more than 3 words for one variable
 +
 +
== Coding Style and Standards ==
 +
* The following will serve as an example of our coding standard:
 
<big><syntaxhighlight lang="cpp">
 
<big><syntaxhighlight lang="cpp">
−
int a;
+
#ifndef __FILENAME_H__
−
int b;
+
#define __FILENAME_H__
−
CDialog D;
+
 
 +
 
 +
class example {    // There will be a space after every class identifier for the definition
 +
  public:
 +
    int _data;    // Member variables should start with an underscore
 +
    int _arraySize // Use meaningful names for variables when applicable and use lower Camel Case
 +
    int _width;    // Every object have its own type
 +
    char* _pArray; // Pointers should have * part of the type
 +
    void display():
 +
};
 +
 
 +
void example::display() {  // There will be a space after every function identifier for the definition
 +
}
 +
 
 +
#endif
 +
 
 +
...
 +
 
 +
#include <iostream>
 +
#include <cstring>
 +
using namespace std;
 +
 
 +
int main() {
 +
    int a = 0;             // Indentation is 4 spaces
 +
    int b = 1;             // NO Tab characters allowed! Replace every tab character with 4 spaces.
 +
    char name[] = "Spoom";
 +
                            // Put a newline after variable declaration
 +
    if(a > b ? a : b) {
 +
        a = a * b;            // Put a space between EVERY variable and operator
 +
    }
 +
                            // Put a newline after a control structure
 +
    if(!strcmp(name, "Spoom")) {
 +
        cout << "Welcome, Spoom!" << endl; // Every statement within a control structure will
 +
    }                                    // be wrapped in braces, even if there is only 1 line
 +
    else {
 +
        cout << "Get out." << endl;
 +
    }
 +
 
 +
    return 0;
 +
}
 
</syntaxhighlight></big>
 
</syntaxhighlight></big>
  

Revision as of 14:20, 21 October 2013


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

Team Name

Project Marking Percentage

  • due right after study break

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

Repository

Master Branch Status

Status

Open : Oct 19th,2013 12:51 I upload prototype files and test files:2 and 3.

  • Open/Closed
    Open: you can merge now.
    Closed: Wait for the repo to get opened

Logs

  • DateTime, Merged/being Merged by full name, ircnick: mynick, any other info

Coding Style and Standards

  • No Tab Character allowed. (replace tabs with 4 spaces)
  • Each object must have its own type:
  • Open { in the same line
  • Close } in the next line
  • Start else in the next line
  • 2 line break for new function
  • Declare variable type only in prototyping
  • Using namespace cio
  • Variables rules
    • start with flag p_, l_ (parameter, local)
    • class variable start with _
    • start with lower character
    • use upper character from first letter of each word (from second word)
    • remove vowel in a variable
    • no more than 3 words for one variable

Coding Style and Standards

  • The following will serve as an example of our coding standard:
#ifndef __FILENAME_H__ 
#define __FILENAME_H__


class example {    // There will be a space after every class identifier for the definition
  public:
    int _data;     // Member variables should start with an underscore
    int _arraySize // Use meaningful names for variables when applicable and use lower Camel Case
    int _width;    // Every object have its own type
    char* _pArray; // Pointers should have * part of the type
    void display():
};

void example::display() {  // There will be a space after every function identifier for the definition 
}

#endif

...

#include <iostream>
#include <cstring>
using namespace std;

int main() {
    int a = 0;              // Indentation is 4 spaces
    int b = 1;              // NO Tab characters allowed! Replace every tab character with 4 spaces.
    char name[] = "Spoom";
                            // Put a newline after variable declaration
    if(a > b ? a : b) {
        a = a * b;            // Put a space between EVERY variable and operator
    }
                             // Put a newline after a control structure
    if(!strcmp(name, "Spoom")) {
        cout << "Welcome, Spoom!" << endl; // Every statement within a control structure will
    }                                     // be wrapped in braces, even if there is only 1 line
    else {
        cout << "Get out." << endl;
    }

    return 0;
}

Team Members

Team Name (Rank S)
First Name Last Name Section Seneca Id wiki id IRC nick Blog URL
Soohyun Ahn B sahn6 Soohyun Ahn IrcNick Soohyun's Blog
Nak Gui Choi B ngchoi Nak Gui Choi ngchoi freeppro's C++ Programming Blog
Yunki Lee B ylee80 Yunki Lee yunki OOP344-SENECA
Hyunsu Lee B hlee125 Hyunsu Lee hlee125 Noname Blog

tasks

task name

  • task description
  • being done by team member name / not assigned
  • status


meetings

  • latest will be on top

topic, date

Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=Team_U_-_OOP344_20133&oldid=101201"