Difference between revisions of "OOP344 - Success - 20102"

From CDOT Wiki
Jump to: navigation, search
(Rules to follow)
(created message board, and added message to board to team page)
Line 3: Line 3:
  
 
Short link for our team page: bit.ly/s_ss
 
Short link for our team page: bit.ly/s_ss
 +
== Message board ==
 +
Hey members of team Success,
 +
 
 +
The assignment is actually really simple. The purpose is that everyone has to commits a piece of code. Since there are ten simple functions, therefore everyone pick 2 functions and commit it to the project. Just remember for each function you pick, it has to done for all platform. The solutions for the functions for any platform are found in Fardad’s repo.  I also prepared a table in project development page on our team page for you to identify which functions you are committing. I also prepared a skeleton of iof.c in trunk, so you can just fill in the blanks, compile it, and then commit it. Once everyone has committed a piece of code, then we’ll move on from there.
 +
 +
Sincerely,
 +
Jason Quan
 +
 
[[File:SuccessKey.jpg|200px|thumb|right|Success is the Key]]
 
[[File:SuccessKey.jpg|200px|thumb|right|Success is the Key]]
  

Revision as of 07:47, 4 June 2010


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

Team Success

Short link for our team page: bit.ly/s_ss

Message board

Hey members of team Success,

The assignment is actually really simple. The purpose is that everyone has to commits a piece of code. Since there are ten simple functions, therefore everyone pick 2 functions and commit it to the project. Just remember for each function you pick, it has to done for all platform. The solutions for the functions for any platform are found in Fardad’s repo. I also prepared a table in project development page on our team page for you to identify which functions you are committing. I also prepared a skeleton of iof.c in trunk, so you can just fill in the blanks, compile it, and then commit it. Once everyone has committed a piece of code, then we’ll move on from there.

Sincerely, Jason Quan

Success is the Key

Project Development

Project Development Page

IRC meetings

IRC meeting logs

Freenode channel : #OOP344Success

Please set time in this table when you are usually available for IRC meetings (put your ID - B,C,D or E).

- SUN
MON
TUE
WED
THU
FRI
SAT
09:00 BC ABC B - - - ABC
10:00 BC ABC B - - - ABC
11:00 BC ABCD B - - - BCD
12:00 BE BCDE B - - - BCDE
13:00 BE BDE B - - - BDE
14:00 BE BDE BD - - - BDE
15:00 BE BCDE B DE D ABCDE BCDE
16:00 BE BCDE B DE D ABCDE BCDE
17:00 ABE ABCDE B ADE ADE ABCDE ABCDE
18:00 ABE ABCDE ABE ADE ABDE ABDE ABCDE
19:00 ABE ABCDE ABCE ABDE ABDE ABDE ABCDE
20:00 ABE ABCE ABCE ABCE ABCE ABCE ABCE

Member List

Success - Member list
ID Last Name Name Seneca Username Section Blog Url IRC Nick SVN ID My Contributions Role
A Pliats Aleh apliats A http://oleg-oop.blogspot.com/ oleg_pliats apliats Contributions
B Quan Jason jquan4 A http://jasonquan.wordpress.com/ JQuan jquan4 Contributions
C Schranz Matthew mjschranz A OOP344 Blog Posts mjschranz mjschranz Contributions
D Balzamova Irina ibalzamova A http://bikarin.blogspot.com/ iIra ibalzamova Contributions
E Park Hong Geung hgpark A http://goldenration.wordpress.com/ goldenration hgpark Contributions

Email All Memebers

Rules to follow

(this is just an example, lets discuss it)


1. Two spaces for indentation

example:

 int main 
 {
   int i;
   int j;
   if (i == 0) 
   {
     i = 1;
   }
 }

2. Name variables like this: char myVariable; int tempSize (first letter is small);

3. Do not create variables that are never use

4. Only use breaks in switch statements

5. Begin each class with #ifndef (we will learn it later)

6. Do not use redundant statements (i.e: if (x != 0) because it same as if(x) )

7. Here is example How to set up tab spaces but please put 2 instead of 3.

8. Do not create several variables in one line

int a,b; //BAD

int a; //GOOD

int b; //GOOD