Difference between revisions of "OOP344 - HOTYS - 20102"

From CDOT Wiki
Jump to: navigation, search
(Coding Style Rules: - Added link to setting up tab settings)
(IRC Schedule/Log: updated Meeting schedule)
Line 42: Line 42:
== <big>IRC Schedule/Log</big> ==
== <big>IRC Schedule/Log</big> ==
[http://zenit.senecac.on.ca/wiki/index.php/OOP344_-_HOTYS_IRC_Logs_-_20102 IRC Page]
Group meetings will be held on Sundays at 12pm in #seneca-HOTYS.<br />
Logs can be found [http://zenit.senecac.on.ca/wiki/index.php/OOP344_-_HOTYS_IRC_Logs_-_20102 here]
==<big>Coding Style Rules</big>==
==<big>Coding Style Rules</big>==

Revision as of 19:19, 23 May 2010

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

This is team HOTYS homepage!!!

The Name of the team is derived from the first letter of each group member's name:

Han Chul Kim
Osman Mirza
Tony Kim
YuJin Jeong
Stephanie Law

Member List

OOP344 - 2010 Team HOTYS -
Name Seneca
Section Blog Url IRC Nick My Contributions
a Kim Han hckim3 A http://hckim.wordpress.com/ han3 Hckim3
b Mirza Ozzy omirza A http://0zzym.wordpress.com/ OzZy_M OzZy
c Kim Tony kjkim A My Blog TonyKim kjkim
d Jeong YuJin yjeong A Spirit & Soul YuJin Takeiteasy
e Law Stephanie slaw12 - A My Blog- Slaw12 slaw12

Team Project

Team Project


Discussion Page

IRC Schedule/Log

Group meetings will be held on Sundays at 12pm in #seneca-HOTYS.
Logs can be found here

Coding Style Rules

Every file should have a function header with:

  • File name
  • Programmer Full name
  • Date last modified


By: Full Name
Date Last Modified: 9:59 AM April-15-10
Description of what is in the file

Variable names should be meaningful so additional comments are not necessary to explain what the variable does.


  int nNum; //Bad
int nNumOfTypes //Good

A lower case prefix should be fitted to the variable name to help describe it at a glance:

Prefix Data Type Example
n int nNumOfSignals
c char cTypeMode
b boolean bIsTrue
f float fLength
d double dWidth
s C-Style null terminated string
OR a String object
p pointers pnNumOfSignals
m_ Data Member/
Instance Variable

All variable declarations should be done on their own lines!

There should be NO single character names for variables (Ex: i, j, k, etc) except for arbitrary counters, such as for for loops

All const and #define Variable names should be in All Caps


  const int nMAX_TRIPS;
#define MAX_TRIPS 1

Pointers should be declared in C++ style:


  int* x;
int * x; OR int *x;

Class names should be all lower case except for the first letter, which should be upper case.

Function names should have meaningful names (They do not require prefix).

Function names Should be all lower case except for the First letter of each Word.


getChar(); OR Getchar();

Each function should have only one point of entry and one point of exit! I.E. There should be only 1 return statement in each function.

Each function should have a header describing what it does.

Use Inline comments to describe hard to read code. All inline code should be set to the same indention as the code it is describing.



Opening braces should be on the same line as the defining function/if/else if/etc statement.


  void FunctionOne(int){
if (x > y){
void FunctionOne(int)
if (x > y)

There should be NO use of the tab character!!! Each indent should be 3 blank spaces!

This shows how to set up tab settings