Team Team - OOP344

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

Team Team - Member list

Last Name	Name	Seneca Username	Section	Blog Url	IRC Nick	SVN ID	My Contributions	Role
Seifried	David	dseifried	B	http://dseifried.blogspot.com	Jangalang	...	Contributions	Team Contact
McDorman	Brendan	bmcdorman	B	http://rift-tlosam.blogspot.com/	Kuat	...	Contributions	Team Contact
Woodley	Carolyn	cwoodley1	B	http://carolynwoodley.blogspot.com	CWoodley	...	Contributions
Cohen	Bryan	bmcohen	B	http://bmcohen.blogspot.com	bmcohen	...	Contributions
Kim	Taehoon	tkim28	B	http://hoonkoon.blogspot.com/	Hoongoon	?	Contributions
Khamar	Ashutosh	amkhamar	B	http://ash4chilled.blogspot.com	Ashu	...	Contributions

IRC

Our first IRC meeting with Fardad is on Tuesday January 26th 2009 at 20:00 to 22:00.

Rules

• NO USING TABS!

   * Rule of thumb for spacing: Four spaces for an indentation, not eight.

• One Type for One Field Definition
• Always use Valgrind for testing once a piece compiles. (Valgrind is a linux tool which checks for memory leaks)
• Make code legible and provide a sufficient explanation of what a block does.
• Put brackets on their own line, as it makes code easier to read for everyone

ex: for (int i = 0; i < 4;i++)
    {
          code here
    }

• Make variable names meaningful/understandable for everyone (not just yourself)

Assignment 1

I think we should get a rough of idea of what simple functions each of us is going to be working on, to prevent any of us from accidentally working on the same function as someone else. Just put what function(s) your going to be working on beside your name below:

• Dave:
• Brendan:
• Carolyn:
• Brian:
• Taehoon:
• Ashutosh: