EECS 381 - Object-Oriented and Advanced Programming - Winter 2013

Lecture: TTh 3:00 - 4:30, 1014 DOW
Overflow Lecture time (Discussion): T 4:30-5:30, 1014 DOW

David Kieras: 3641 CSE Building
763-6739
eecs381help at the usual umich and edu address
kieras at the usual umich and edu address

Administrative

How to do Well on the Projects
Autograder Information and Policies
The EECS 381 Submission Program How to submit your projects!
Sample Code Quality Checklist (pdf)
When your code is evaluated for quality, it will be done using a checklist similar to this one, but with additional project-specific checks. Be sure to check your code against the specifications not just for behavior, but also for the recommendations and requirements for how it is written.

Autograder Output and Error Messages Explanations of messages produced by the Autograder.
Finding Bugs in your Projects An essay on elementary program inspection and testing (pdf).
How to Debug A brief introduction to debugging.
Debugging FAQ Some of the most common bugs explained.
Array and Pointer Bugs The nasty part of C and C++.
Error Message FAQ Some basics of understanding error messages.
How to Get Help by Email Read this before sending email to get help on a project.
Before you send for help... Save time! You may be able to answer the question yourself.

Google's C++ Coding Standards A good example of corporate coding standards - showing how they use C++ in their environment.
A blog entry pointing to Google's C++ Coding Standards Some background and comments.
An Introduction to Bloomberg's BDE Coding Standards Bloomberg uses C++ heavily for good performance, and has developed an open-source alternative to the Standard Library ( homepage , wiki).