Jump to: navigation, search

Team Team - OOP344

227 bytes added, 21:13, 28 January 2010
Added some rules for team
* 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)
== Issues ==

Navigation menu