== <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

|} == 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. === 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.  {Amy Ward | class="wikitable" border="1"|+ Discussion! Name !! CommentAmyWard11

| fmDeOliveira Minoo Ziaei || 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).mziaei53

| MattAdams Timothy Catibog || 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 savedjordyy.catibog

| Mziaei1 Felipe de Oliveira || 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!"); } }feliploko

 | Timothy Andrew Misko || 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.ammisko

=== Put the pointer identifier(*) right after the target variable type. =<big>IRC</big> ==Pointers are hard enough to deal withOur IRC channel is #oop344_!you on freenode. It only makes it more complicated if they Please join the channel whenever you are declared differently throughout the codeon IRC.

=== (Discussion: Use of iterating variables on for loops) ===There are two major ways of dealing with the iteration variable on '''for''' loops. We should come before trying to a consensus on how to deal with it on our projectjoin again.

Option 1=== [http: 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<5; i++) printf("zenit.senecac.on."); ca/wiki/ Prints index.php/Team_!YOU_-_IRC_Meetings IRC Meetings] ===Our first meeting was on Wednesday, January 27th, from 10pm to midnight.On the following weeks, we will meet regularly on Mondays from 8pm to 10pm... printf("%d",i); // Prints 5

Option 2To view information about past or upcoming meetings, please visit [http://zenit.senecac.on.ca/wiki/index.php/Team_!YOU_-_IRC_Meetings 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/index.php/ Once the loop is done, variable i cannot be accessed anymoreTeam_!YOU_-_IRC_Meetings].

{| class="wikitable" border="1"<big>Team Programming Standards</big> ==|+ Discussion! Name !! Comment|-| 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 An area for listing our teams programming standards that 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 will use when constructing the loopproject.|-| ammisko || I like option 1 better (I changed it a bit)Please follow these rules when writing code for this project. I think This will make 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 us to use a loop variable from outside help each other and collaborate in 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 thinkwhole process.|-

| MattAdams || I like both ways=== [http://zenit. I use option1 when I need to use the counter for something elsesenecac. And I use option2 when I need to right a quick for loopon. As for a standard, I think option1 should be used, that way all of the variables are declared at the top of every function, and that way we don't have to copy the counter to another variableca/wiki/index.php/Team_!YOU_-_Official_Standards Official Team !You Programming Standards] ===

|To view a list of our agreeded upon programming standards, please visit [http://zenit.senecac.on.ca/wiki/index.php/Team_!YOU_-|}_Official_Standards http://zenit.senecac.on.ca/wiki/index.php/Team_!YOU_-_Official_Standards].

| MattAdams || I also agree w== <big>The Project</ 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|}big> ==

=== (Discussion: Use of comments) ===When should we use double slash (//) An area for us to post information and when should we use slash-asterisk (/* */)?links for our team project.

{| class="wikitable" border="1"|+ Discussion! Name !! Comment|-| fmDeOliveira || I prefer using // Our page 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 basic input output library, the single-line comment would not be interpreted as the end first part of the block comment)our project.|-

=== [[!You's OpText - OOP344 | 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.OpText]] ===

|====Part1: [http://zenit.senecac.on.ca/wiki/index.php/Create_Class_Prototypes_-_!You_-_OOP344 Create Class Prototypes]====

| Mddaniels|| What you need to remember is that we are coding in C the ====Part2: [http:// for single line comments does not work in Czenit. All coments need to be in the senecac.on.ca/* *wiki/ format. Also try and use the comments to reflect the Art of Programmingindex. php/Code_all_member_functions_-_!You_-_OOP3444 Code should be written that any programmer can look at the code and understand what is going on.all member functions]====

====Part3: Code BForm functions===={|-class="wikitable" border="1"|}+ Class Member Functions

=== (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(","); } Option 2: 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 (a > 0) { printf("."); } else { printf(","); } {! Tasks | class="wikitable" border="1"|+ DiscussionMembers Working On It !! Name Status !! CommentDue Date

| fmDeOliveira BForm::edit || I prefer option 2.MattAdams || In Progress || -

| BForm Constructor/Destructor || Minoo || committed || March 23, 2010 midnight|- | MattAdams BForm::display() ||Amy | Option 2 all the way.| committed || March 23, 2010 midnight

 | Mziaei1 BForm::add() x2 || Agree with option 2.Timothy || committed || March 23, 2010 midnight

 | Mddaniels BForm::editable, fieldNum, curField, operator[] || Felipe || 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 <big>Helpful External Links</big> == 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 /><br />{| class="wikitable" border="1"|+ Code Example! Name !! Code|-| MattAdams || [http://matrixwww.senecacmicrosoft.on.cacom/~mdadams1express/assign4.zip assign4.zip]|-| Mziaei1 || [http:Downloads//matrix.senecac.on.ca/~mziaei1/Assign4/a4.zip a4.zipMicrosoft Visual Studio Express Edition Download]|-|}