Difference between revisions of "Team H - OOP344 20133"

From CDOT Wiki
Jump to: navigation, search
(Coding Style and Standards)
(Coding Style and Standards)
Line 24: Line 24:
 
CDialog D;
 
CDialog D;
 
</syntaxhighlight></big>
 
</syntaxhighlight></big>
** With regards to space characters, standard will be as follows:
+
* With regards to space characters and opening and closing brackets ,standard will be as follow:
 
<big><syntaxhighlight lang="cpp">
 
<big><syntaxhighlight lang="cpp">
if(a == b) {
+
if(a == b) {//There should be a space between each meaningful variable and operator and so on
 
   x = y * z; // 2 spaces for indentation
 
   x = y * z; // 2 spaces for indentation
 
}
 
}
Line 35: Line 35:
 
   public:
 
   public:
 
   int _a; // member variables should start with an underscore
 
   int _a; // member variables should start with an underscore
   int _arraySize // use meaningful names for variables when applicable and use camel notation
+
   int _arraySize; // use meaningful names for variables when applicable and use camel notation
 
   char* _pArray; // pointers should have '*' part of the type
 
   char* _pArray; // pointers should have '*' part of the type
 
};
 
};
Line 41: Line 41:
 
* For the safeguard for header files, we will use the following:
 
* For the safeguard for header files, we will use the following:
 
<big><syntaxhighlight lang="cpp">
 
<big><syntaxhighlight lang="cpp">
 +
H_FILENAME_H_
 +
</syntaxhighlight></big>
 +
 +
  
 
== Team Members ==
 
== Team Members ==

Revision as of 16:46, 18 October 2013


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

Team H

Project Marking Percentage

  • Group work: 50%
  • Individual work: 50%

Total 100%

Repository

Master Branch Status

Status

  • OPEN

Logs

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

Coding Style and Standards

  • File names must be lowercase.
  • No Tab Character allowed. (replace tabs with 2 spaces)
  • Each object must have its own type:
int a;
int b;
CDialog D;
  • With regards to space characters and opening and closing brackets ,standard will be as follow:
if(a == b) {//There should be a space between each meaningful variable and operator and so on
  x = y * z; // 2 spaces for indentation
}
  • With regards to classes, standard will be as follows:
class example {
  public:
  int _a; // member variables should start with an underscore
  int _arraySize; // use meaningful names for variables when applicable and use camel notation
  char* _pArray; // pointers should have '*' part of the type
};
  • For the safeguard for header files, we will use the following:
 H_FILENAME_H_


Team Members

Team Name (team x)
First Name Last Name Section Seneca Id wiki id IRC nick Blog URL
Jungmin Ji A jjungmin Ji Jungmin Mistysnake Breeze
Chiyoung Choi A cchoi12 Chiyoung Choi Chris-choi
Mauli Shah A mshah24 Mauli Shah mshah

http://mauli9shah.wordpress.com/

Tasks

task name

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


Meetings

  • latest will be on top

topic, date

date