Difference between revisions of "OOP344 20131 Oopers"

From CDOT Wiki
Jump to: navigation, search
(Coding Guidelines)
(Team Members)
Line 41: Line 41:
  
 
{| class="wikitable sortable" border="1" cellpadding="5"
 
{| class="wikitable sortable" border="1" cellpadding="5"
! First Name !! Last Name !! Team Name !! Section !! Seneca Id !! wiki id !!  IRC nick !! GITHUB ID !! Blog URL
+
! First Name !! Last Name !! Team Name !! Section !! Seneca Id !! wiki id/Contributions !!  IRC nick !! GITHUB ID !! Blog URL
 
|-
 
|-
 
|[[User:Peter Huang|Peter]]||Huang||[http://zenit.senecac.on.ca/wiki/index.php/OOP344_20131_Oopers Oopers]||B||[mailto:phuang19@myseneca.ca?subject=oop344 phuang19]||[[Special:Contributions/Peter Huang|Peter Huang]]||phuang||peter-huang|| [http://peter-huang.blogspot.ca/ Peter Huang's Blog]
 
|[[User:Peter Huang|Peter]]||Huang||[http://zenit.senecac.on.ca/wiki/index.php/OOP344_20131_Oopers Oopers]||B||[mailto:phuang19@myseneca.ca?subject=oop344 phuang19]||[[Special:Contributions/Peter Huang|Peter Huang]]||phuang||peter-huang|| [http://peter-huang.blogspot.ca/ Peter Huang's Blog]

Revision as of 03:54, 14 February 2013


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

Oopers (Team 8)

Repository

+++ Git Repository ID: Ooper (https://github.com/Seneca-OOP344/8-Ooper.git) +++

Coding Guidelines

1) Software: Visual Studio 2010.

2) Blocking: Open and closed brackets {} should each be in a new line. Single syntax in functions are to be blocked as well.

Examples:

   if(whatever) do this; //bad
   if(whatever) 
      do this; // bad
   if(whatever)
   {
      do this:
   } // good

3) Identation: 3 spaces!

4) Variable Names:

  • Private instance var - _dataExample - starts with underscore, first word is in lowercase, first letter of second word is uppercase (rest of characters are lowercase), etc.
  • Public functions - GetData() - first letter of each word in function name is uppercase (rest of characters are lowercase).
  • Each variable, when created, should be written in one line

Examples:

   int a; // good
   int a, b. c; //bad

5) Seneca Honesty Policy, Date, Professor Name, Student (or Group), Section, Class should be in a comment on the top of every source file (.cpp and .h)

Team Members

Email to all members

First Name Last Name Team Name Section Seneca Id wiki id/Contributions IRC nick GITHUB ID Blog URL
Peter Huang Oopers B phuang19 Peter Huang phuang peter-huang Peter Huang's Blog
Mark Hom Oopers B mahom Mark Hom mahom mahom21 OOP344 bLoG
Shay Trotsky Oopers B strotsky Shay Trotsky strotsky strotsky OOP344 Rules
Curtis Wilson Oopers B cjwilson3 Curtis Jordan Wilson SL37 Curtis37 Curtis' Blog

Agenda

Meetings

Discussion