== <big>Team Members </big> ==

|+ OOP344 - 2010 Team !YOU-  [mailto:mdadams1@learn.senecac.on.ca,mddaniels@learn.senecac.on.ca,fmdeoliveira@learn.senecac.on.ca,ammisko@learn.senecac.on.ca,amward1@learn.senecac.on.ca,mziaei1@learn.senecac.on.ca,nsimmalavong@learn.senecac.on.ca,tjcatibog@learn.senecac.on.ca Email All]

| (A)Adams|| [http://zenit.senecac.on.ca/wiki/index.php/User:Mdadams1 Matthew]|| [mailto:mdadams1@learn.senecac.on.ca mdadams1]|| A || http://www.tandemwebdesign.ca/blog || MattAdams|| [[Special:Contributions/mdadams1 | Contributions]]

| (A)Catibog|| [http://zenit.senecac.on.ca/wiki/index.php/User:Tjcatibog Timothy]|| [mailto:tjcatibog@learn.senecac.on.ca tjcatibog]|| A|| http://tjprogramming.blogspot.com/ || tjcatibog|| [[Special:Contributions/tjcatibog | Contributions]]

| (A)De Oliveira|| [http://zenit.senecac.on.ca/wiki/index.php/User:fmdeoliveira Felipe]|| [mailto:fmdeoliveira@learn.senecac.on.ca fmdeoliveira]|| A || http://feliploko.wordpress.com/ || fmDeOliveira || [[Special:Contributions/fmdeoliveira | Contributions]]

| (A)Misko|| [http://zenit.senecac.on.ca/wiki/index.php/User:ammisko Andrew]|| [mailto:ammisko@learn.senecac.on.ca ammisko]|| A || http://ammisko.blogspot.com || ammisko || [[Special:Contributions/ammisko | Contributions]]

| (A)Ward|| [http://zenit.senecac.on.ca/wiki/index.php/User:Amward1 Amy]|| [mailto:amward1@learn.senecac.on.ca amward1]|| A || http://amward1.wordpress.com/ || award|| [[Special:Contributions/amward1 | Contributions]]

| (A)Ziaei|| [http://zenit.senecac.on.ca/wiki/index.php/User:Mziaei1 Minoo] || [mailto:mziaei1@learn.senecac.on.ca mziaei1]|| A || http://minooz.wordpress.com/ || Minooz || [[Special:Contributions/mziaei1 | Contributions]]

==<big>Skype</big> = IRC Meetings = {| class="wikitable sortable" border="1" cellpadding="5"We need to decide when we should have our meetings.|+ Skype Name

{! Name !! SkyName |-| Matthew Adams || matt_adams21|-| Amy Ward || class="wikitable" border="1"AmyWard11|+ Discussion-! Name !! Comment| Minoo Ziaei || mziaei53

| fmDeOliveira Timothy Catibog || Evenings work better for me... It is hard to find some time in the morning or afternoon that all or most of us are able to be on IRCjordyy.catibog

| ammisko Felipe de Oliveira || Evening are also good for me. I don't have class later than 320 every day. As long as I know a few days in advance I shouldn't have a problem with meeting any time after 320.feliploko

 | MattAdams Andrew Misko || Evening is probably better, because that is when I do all of my programming. I normally work from Thursday to Sunday, so early week is better for me.ammisko

== Team Programming Standards <big>IRC</big> ==An area for listing our teams programming standards that we will use when constructing the projectOur IRC channel is #oop344_!you on freenode. Please follow these rules when writing code for this project. This will make it easier for us to help each other and collaborate in join the whole processchannel whenever you are on IRC.

=== Declare only one variable in each line. ===This makes it easier The channel is restricted to scan Fardad and the code team members. There is an access list that will automatically kick and find ban anyone not listed. For this reason, we should always make sure we are using our official IRC nicks (or one within our nick group) and that we are identified with the type of a variable that you see somewhere else in nickserv (/nickserv identify ''mypassword'') before issuing the codejoin command.

Do: int If you are getting a; int b = 0; int c = a;message that you are banned on our channel, make sure you are identified and then issue the command

Don't: int a, b = 0, c = a;/chanserv unban #oop344_!you

=== Do not use tabs when indenting[http://zenit. senecac.on.ca/wiki/index.php/Team_!YOU_-_IRC_Meetings IRC Meetings] ===The tab space is interpreted different across different software and operating systemsOur first meeting was on Wednesday, January 27th, from 10pm to midnight. Use normal spaces On the following weeks, we will meet regularly on Mondays from 8pm to add indentation instead10pm.

==== (Discussion: Indentation) ==<big>Team Programming Standards</big> ==Something simple, but An area for listing our teams programming standards that should be standard for all pieces of the code.  {| class="wikitable" border="1"|+ Discussion! Name !! Comment|-| fmDeOliveira || I usually put two spaces for a new indent, and keep a blank line between new big blocks of code and whatever comes before it (usually an if statement, a for loop, or we will use when constructing the signature of a function)project.|-| MattAdams || Please only indent to 4 spaces. If we all use the same indenting, follow these rules when it comes to putting our writing code together it will looks the samefor this project.NOTE: Most text editors have the option to change tabs to spaces, so you are still able to press the tab key, however it This will convert make it easier for us to spaces when help each other and collaborate in the file is savedwhole process.|-| Mziaei1 || I actually agree with 2 spaces more than 4 spaces. There was an example here before!! main() { for (i = 0; i <10; i++) { printf("Hi!"); } }|-|}

=== Put the pointer identifier(*) right after the target variable type[http://zenit. senecac.on.ca/wiki/index.php/Team_!YOU_-_Official_Standards Official Team !You Programming Standards] ===Pointers are hard enough to deal with. It only makes it more complicated if they are declared differently throughout the code.

DoTo view a list of our agreeded upon programming standards, please visit [http: int* p1; char* p2;//zenit.senecac.on.ca/wiki/index.php/Team_!YOU_-_Official_Standards http://zenit.senecac.on.ca/wiki/index.php/Team_!YOU_-_Official_Standards].

Option 1: Declare the variables outside the loop; initialize them inside the loop; keep their exit values for future use. int i; // counter for (i = 0; i= <big>The Project<5; i++) printf("."); // Prints ..... printf("%d",i); // Prints 5big> ==

Option 2: Declare An area for us to post information and initialize variables inside the loop; lose the variable at the end of the loop scope; links for (int i = 0; i<5; i++) printf("."); // Once the loop is done, variable i cannot be accessed anymoreour team project.

{| class="wikitable" border="1"|+ Discussion! Name != [[Team ! Comment|YOU -BIO Library | fmDeOliveira || I definitely prefer option 2. It is much easier to keep recycling the loop variables without having to worry if they already exist or not. In case we need the value of the loop variable after the loop is done, we should just copy it to another variable before the end of the loop.|-| ammisko || I like option 1 better (I changed it a bit). I think it looks cleaner and is much easier to read for someone who doesn't know what the code does (especially with comments). Also what if we need to use a loop variable from outside the for loop? Or if we need to use the first part of the for-loop for other code? Option 1 could accommodate that better I think.|-Basic Input Output Library]] ===

| MattAdams || I like both ways. I use option1 when I need to use Our page for the counter for something else. And I use option2 when I need to right a quick for loop. As for a standardbasic input output library, I think option1 should be used, that way all of the variables are declared at the top first part of every function, and that way we don't have to copy the counter to another variableour project.

|=== [[!You's OpText -OOP344 |}OpText]] ===

=== (Discussion=Part1: Variable names) [http://zenit.senecac.on.ca/wiki/index.php/Create_Class_Prototypes_-_!You_-_OOP344 Create Class Prototypes]====How should we name the variables that we create on our project?

|+ Discussion! Name !! Comment|-| fmDeOliveira || I suggest we avoid abbreviations, since what might be obvious for some could be confusing for others. Full words or short expressions could be used where the first letter is always lower case, and the first letter of the following words are upper case. Examples: cost, totalPrice, numberOfPeople.|- | MattAdams || I also agree w/ Felipe. Using Camle notation is a nice and easy way to name variables. However, I would have said numOfPeople, instead of 'numberOfPeople'. As for #define goes. Use UPPER case, and separate words by the underscore(_). ie. #define ISBN_LENGTH, #define AREA_MAX, #define MAX, #define LENGTH|} === (Discussion: Use of comments) ===When should we use double slash (//) and when should we use slash-asterisk (/* */)?Class Member Functions

{! Tasks | class="wikitable" border="1"|+ DiscussionMembers Working On It !! Name Status !! CommentDue Date

| fmDeOliveira BForm::edit || MattAdams || In Progress || I prefer using // for single-line comments and /* */ for blocks of commented code. This would avoid problems commenting out blocks of code that already have single-line comments (the end of the single-line comment would not be interpreted as the end of the block comment).

| BForm Constructor/Destructor || Minoo || committed || March 23, 2010 midnight| MattAdams - |BForm::display() | I also like using // for end of the line comments to slitly explain whats going on| Amy || committed || March 23, and use /* */ for commented out code, as well as explaining a certain block of code that is confusing to understand.2010 midnight

 | Mziaei1 BForm::add() x2 || I agree with both Felipe and Matt.Timothy || committed || March 23, 2010 midnight

=== (Discussion: Nesting) ===How do we deal with else statements? Option 1: else right after the end of the if block if (a <big> 0) { printf("."); } else { printf(","); } Option 2: else on a line below the end of the if block if (a Helpful External Links</big> 0) { printf("."); } else { printf(","); } {| class="wikitable" border="1"|+ Discussion! Name !! Comment|-| fmDeOliveira || I prefer option 2.|- | MattAdams || Option 2 all the way. |-

| Mziaei1 || Agree with option 2[http://www.|}microsoft.com/express/Downloads/ Microsoft Visual Studio Express Edition Download]