Changes

<big><big>'''[http://zenit.senecac.on.ca/wiki/index.php/Team_!YOU_-_Official_Standards Official Standards]'''</big></big> - Go to team's official programming standards.

= Team !You Programming Standards Discussion =Committing Practices ==When many people work together on the same project, ideally only a couple of them are responsible for committing the code. Although our team has only 8 members, it is probably a good idea to give the committing responsibility to only one or two members at once. Fardad has suggested that we rotate this responsibility, and I think we should try that. To make it possible, I have thought of a way to make it work.

=== Declare only one variable in each line* Each week two of us are responsible for committing. ===This makes it easier to scan The order we alternate this role could be random, or we could go down the code and find the type of a variable that you see somewhere else in team member list as we did for dividing the codesimple functions among us.

Don* If you finished something in your branch that is worth committing but it't: int s not your turn to commit yet, create adiscussion on this page with your name and the files you worked on. That way we can all check your work on your branch and comment possible changes here. Once everyone has looked at it, b = 0, c = a;one of the committers can finish the job.

=== 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* Always document your commits, so we have some control in case something goes wrong.

===Committing Agreement===Here is the result of discussion on "Committing"#How often#*Every Monday that we have our weekly IRC meeting, those people who are in charge of committing for that week,will be in the meeting to make sure there isn't anything wrong with the codes and will commit them right away.#Who#*We will go by the order of the team's member list. Every week, 2 members are responsible for committing.#How#*Those people that are done with their part of code, will upload their code with their name and their files in the [http://zenit.senecac.on.ca/wiki/index.php/Team_!YOU_-_Codes Codes' snippet] page, and will let everybody else know that they have finished - in case somebody wanted to comment any changes.<br/>{| class="wikitable" border="1"|+ Committing Schedule! Commit-er member !! Date !! Date|-| MattAdams || |||-| tjcatibog || |||-| CDNPadawan || || |-| fmDeOliveira || || |-| ammisko || |||-| nsimmalavong || || |-| award || |||-| Minooz || || |}<br/>  = Coding Help =An area for working out problems with code. == (ammisko) Problem Compiling With bio_init(); ==I am having a problem getting my project code to compile in VCC and BCC. My main looks like...  main(){ bio_init(); int i = 0; /* line 58 */ printf("Press a key to return its key code, or press esc to exit loop.\n\n"); while (i != 27){ i = bio_getch(); printf("Key Code Returned: %d\n", i); } bio_end(); return 0; } I have also included <stdio.h> higher up in the biomain.c  When I attempt to compile the above code I get an error message like (this is VCC): g:\school\oop344\prj_trunk\biomain.c(58) : error C2143: syntax error : missing ';' before 'type'  If I comment out bio_init(); in the main, the program compiles fine and runs exactly like it should. The code is in my branch if you want to see the whole thing.  {| class="wikitable" border="1"|+ ! Name !! Comment|- | ammisko || Anyone have any ideas? |}    = Old Discussions = == IRC Meeting Discussion =={| 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.|- | 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.|- | Mziaei1 || Evenings are better for me too. Any evening, unless something unexpected happens.|-| Timothy || 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. |- | Mddaniels || 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 available|- | Nsimmalavong || Anytime after 7 pm is good except on Tuesdays and Fridays, it would be preferred after 9 because I tend to work later those days. I can be made available at anytime on IRC outside those times if needed.|- | Amward1 || Evenings are good.|-|}  == Team !You Programming Standards Discussion == === (Discussion: Indentation) ====