Changes

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

| (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]]

== IRC <big>Discussions</big> ==Our IRC channel is #oop344_!you on freenode. Please join visit the channel whenever you are [http://zenit.senecac.on IRC.ca/wiki/index.php/Team_!YOU_-_Discussions Discussion Page] often, so we can share resources and opinions with others in between our weekly meetings.

{| class="wikitable" border="1"|+ Discussion! Name !! Comment|-| fmDeOliveira || 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 IRC.|-| ammisko || 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.|-<big>Skype</big> ==

{| MattAdams || 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.class="wikitable sortable" border="1" cellpadding="5"|-+ Skype Name

| Timothy Matthew Adams || Any evening or weekend is good for me. Most school days I'm home by 6:30 p.m. at the latest so anytime after that would be perfect.matt_adams21

 | Mddaniels Amy Ward || Evenings are good for me, I have a paper route that keeps me busy until 7pm on Tuesdays and Thursdays but asside from that I'm availableAmyWard11

|} == Team Programming Standards ==An area for listing our teams programming standards that we will use when constructing the project. Please follow these rules when writing code for this project. This will make it easier for us to help each other and collaborate in the whole process. {Minoo Ziaei | class="wikitable" border="1" cellpadding="5"|+ ! Name !! Commentmziaei53

| ammisko Timothy Catibog || What does everyone think about creating a sub-team page for all our programming standards discussions? We could move all our discussions below onto a Team Programming Discussion Page and then only post the standards we all agree upon on the team page. We could do the same for Assignments as welljordyy.catibog

|}     === Declare only one variable in each line. ===This makes it easier to scan the code and find the type of a variable that you see somewhere else in the code. Do: int a; int b = 0; int c = a; Don't: int a, b = 0, c = a;  === Do not use tabs when indenting. ===The tab space is interpreted different across different software and operating systems. Use normal spaces to add indentation instead.  ==== (Discussion: Indentation) ====Something simple, but that should be standard for all pieces of the code.  {Felipe de Oliveira | class="wikitable" border="1"|+ Discussion! Name !! Commentfeliploko

| fmDeOliveira Andrew Misko || 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 the signature of a function).|-| MattAdams || Please only indent to 4 spaces. If we all use the same indenting, when it comes to putting our code together it will looks the same.NOTE: Most text editors have the option to change tabs to spaces, so you are still able to press the tab key, however it will convert it to spaces when the file is saved.|-| 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!"); } }ammisko

| Timothy || What I do in Visual Studio is change the indentation settings to input 2 spaces instead of tabs, and I prefer it this way just in case there is a situation where multiple nested code is required and it's not all running off the page to view it properly.}

| Mddaniels || I myself have always used The channel is restricted to Fardad and the tab just for speed team members. There is an access list that will automatically kick and ease of programmingban anyone not listed. For this reason, plus I like having my code spaced out so we should always make sure we are using our official IRC nicks (or one within our nick group) and that I can locate blocks of code better. But if we are identified with the general opinion is to use two spaces then I will modify nickserv (/nickserv identify ''mypassword'') before issuing the visual studio software to use two spacesjoin command.|-|}

=== Put the pointer identifier(*) right after the target variable type. ===Pointers If you are getting a message that you are hard enough to deal with. It only makes it more complicated if they banned on our channel, make sure you are declared differently throughout identified and then issue the code.command

Do: int* p1; char* p2;/chanserv unban #oop344_!you

=== (DiscussionTo view information about past or upcoming meetings, please visit [http: Use of iterating variables //zenit.senecac.on for loops) ===There are two major ways of dealing with the iteration variable .ca/wiki/index.php/Team_!YOU_-_IRC_Meetings http://zenit.senecac.on '''for''' loops. We should come to a consensus on how to deal with it on our projectca/wiki/index.php/Team_!YOU_-_IRC_Meetings].

Option 1: Declare the variables outside the loop; initialize them inside the loop; keep their exit values == <big>Team Programming Standards</big> ==An area for future listing our teams programming standards that we will usewhen constructing the project. int i; // counter Please follow these rules when writing code for (i = 0; i<5; i++) printf("."); // Prints ..this project.This will make it easier for us to help each other and collaborate in the whole process.. printf("%d",i); // Prints 5

Option 2=== [http: Declare and initialize variables inside the loop; lose the variable at the end of the loop scope; for (int i = 0; i<5; i++) printf("//zenit.senecac.on."); ca/wiki/ Once the loop is done, variable i cannot be accessed anymoreindex.php/Team_!YOU_-_Official_Standards Official Team !You Programming Standards] ===

{| class="wikitable" border="1"|+ DiscussionTo view a list of our agreeded upon programming standards, please visit [http://zenit.senecac.on.ca/wiki/index.php/Team_! Name !! Comment|YOU_-| fmDeOliveira || I definitely prefer option 2_Official_Standards http://zenit. It is much easier to keep recycling the loop variables without having to worry if they already exist or notsenecac. 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 loopon.|-| ammisko || I like option 1 better (I changed it a bit)ca/wiki/index. 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 forphp/Team_!YOU_-loop for other code? Option 1 could accommodate that better I think_Official_Standards].|-

==<big>The Project</big> = (Discussion: Variable names) ===How should we name the variables that we create on our project?

{| class="wikitable" border="1"|+ Discussion= [[Team ! Name !! Comment|YOU -BIO Library | 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.|-Basic Input Output Library]] ===

| 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 Our page for #define goes. Use UPPER casethe basic input output library, and separate words by the underscore(_). iefirst part of our project. #define ISBN_LENGTH, #define AREA_MAX, #define MAX, #define LENGTH

|-| Mddaniels || Defines should always be caps, and camel notation is very good, just as long as the variable names make sense I'll be happy. I got sick and tired of last semester=== [[!You's group giving variable names like "ptr".|OpText -OOP344 |}OpText]] ===

=== (Discussion=Part1: [http: Use of comments) ===When should we use double slash (//) and when should we use slash-asterisk (zenit.senecac.on.ca/wiki/* *index.php/)?Create_Class_Prototypes_-_!You_-_OOP344 Create Class Prototypes]====

|+ Discussion! Name !! Comment|-| fmDeOliveira || 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).|- | MattAdams || I also like using // for end of the line comments to slitly explain whats going on, and use /* */ for commented out code, as well as explaining a certain block of code that is confusing to understand.Class Member Functions

 | MddanielsBForm::edit || What you need to remember is that we are coding in C the // for single line comments does not work in C. All coments need to be in the /* */ format. Also try and use the comments to reflect the Art of Programming. Code should be written that any programmer can look at the code and understand what is going on.MattAdams || In Progress || -

|} === (Discussion: Nesting) ===How do we deal with else statements? Option 1: else right after the end of the if block if (a > 0) { printf("."); } else { printf("BForm Constructor/Destructor || Minoo || committed || March 23,");2010 midnight }|-  Option 2| BForm: else on a line below the end of the if block if (a > 0) { printf("."); } else { printf(","); } Mddaniels example: This is how I was taught in IPC144 by Murray Saul if display(a > 0) { printf("."); } else { printf(","); } {| class="wikitable" border="1"|+ Discussion! Name !! CommentAmy || committed || March 23, 2010 midnight

| fmDeOliveira BForm::add() x2 || I prefer option 2.Timothy || committed || March 23, 2010 midnight

 | MattAdams || Option 2 all the way. |- | Mziaei1 BForm::editable, fieldNum, curField, operator[] || Agree with option 2. Felipe |- | Mddaniels committed || I agree with option 2. Although I am used to coding my braces on seperate linesMarch 23, see my small example above. 2010 midnight

== Code Examples == Below we all will post our OOP244 Assignment 4 from last semester. Please zip all of the files, and upload it. This will help all of us create our coding "rules". I, of all people, know how hard it is to break coding habits. So if we upload examples of how we code, then we can have a better understanding of each other's habits, and create rules that make us all happy. The sooner everyone posts their code, the sooner everyone else can read it, and the sooner we can create our programming rules.<br /big>Helpful External Links<br /big>{| class="wikitable" border="1"|+ Code Example! Name !! Code|-| MattAdams || [http://matrix.senecac.on.ca/~mdadams1/assign4.zip assign4.zip]|-| Mziaei1 || [http://matrix.senecac.on.ca/~mziaei1/Assign4/a4.zip a4.zip]|-| fmDeOliveira || [http://matrix.senecac.on.ca/~fmdeoliveira/a4.zip a4.zip]|-|}

{| class="wikitable" border="1"|+ Discussion! Name !! Comment|-| Mddaniels || The only problem I have with this is that 1) I do not have any code left from previous semesters on my computers due to a system's crash[http://www. If it is really needed then I will write a piece of dummy code in my prefered style and post it here to the team pagemicrosoft.|-| ammisko || I don't have a coding example from last semester either. I took OOP244 a while ago so I'll have to find something to upload from then.|-|}com/express/Downloads/ Microsoft Visual Studio Express Edition Download]