Difference between revisions of "Team Team - OOP344"

From CDOT Wiki
Jump to: navigation, search
(Assignment 1)
(Assignment 1)
Line 63: Line 63:
*Ashutosh: '''Simple: ''' int bio_rows(), int bio_cols() '''Complex: ''' int bio_edit(, ,,,,,,, )   
*Ashutosh: '''Simple: ''' int bio_rows(), int bio_cols() '''Complex: ''' int bio_edit(, ,,,,,,, )   
*Michael: '''Simple: ''' void bio_putch(int c), void bio_putstr(const char *s) '''Complex: ''' int bio_flag(...)
== Issues ==
== Issues ==

Revision as of 20:39, 9 February 2010

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 tkim28 Contributions
Khamar Ashutosh amkhamar B http://ash4chilled.blogspot.com Ashu ... Contributions
Lin Michael mlin25 A http://krazyazn.blogspot.com/ mlin25 ... Contributions
Mirza Umar umirza A http://mar-talks.blogspot.com/ umirza85 ... Contributions


Our first IRC meeting with Fardad is on Tuesday January 26th 2009 at 20:00 to 22:00. From now on meetings will be held on Tuesdays at 8pm until 10pm.

Generally we will try to have our meetings at 20:00 to 22:00 on Tuesdays.


   * 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)
  • At the end of each code block, code what you're ending
ex: for (int i = 0; i < 4;i++)
          code here
    }//end for loop

Assignment 1

First Release Due: February 9th, 2010

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: Simple: int bio_getch (void), void bio_move (...) Complex: void bio_display(...), void bio_displayflag(...)
  • Brendan:
  • Carolyn:
  • Brian:
  • Taehoon:
  • Ashutosh: Simple: int bio_rows(), int bio_cols() Complex: int bio_edit(, ,,,,,,, )
  • Michael: Simple: void bio_putch(int c), void bio_putstr(const char *s) Complex: int bio_flag(...)
  • Umar: