coding_standards - Coding Standards Coding Standards. For :...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon
1 Coding Standards. For : COP 3330. Object oriented Programming (Using C++) http://www.compgeom.com/~piyush/teach/3330 Piyush Kumar Coding Standards | Compile cleanly (no warnings) z Use multiple compilers. gcc/icc suites are installed. | Makefiles are required for each project. Coding Standards | Use of svn is mandatory. (version control) z “The palest of ink is better than the best memory” z Don’t break the build. The code in the version control system (svn) should always compile. | Lot of svn tutorials on the web. z http://artis.imag.fr/~Xavier.Decoret/res ources/svn/index.html z http://centerstageproject.com/wiki/inde x.php/SVN_Tutorial Code Review | Re-Read code. More eyes will help make better quality. Read code from good programmers. You’ll learn and benefit. | It’s best to do code reviews in writing, a simple e-mail can suffice. Correctness | Correct is better than fast.
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 2
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 02/27/2012 for the course CS 251 taught by Professor Staff during the Fall '08 term at Purdue University-West Lafayette.

Page1 / 2

coding_standards - Coding Standards Coding Standards. For :...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online