CPTR 314 Data Structures, Algorithms, and Knowledge Systems

Unless otherwise specified, your solutions to all programming problems must be expressed in C++. You may develop on the platform of your choice, but you should ensure that your submissions build and run correctly under Microsoft's Visual C++ 9.0 (i.e., Visual Studio 2008).
Submitting code that won't compile is a bad thing. If you cannot complete a feature, document the missing functionality and provide at least a method or function stub. From wikipedia (http://en.wikipedia.org/wiki/Method_stub):

A Stub is a routine that doesn't actually do anything other than declare itself and the parameters it accepts and returns something that is usually the values expected in one of the 'happy scenarios' for the caller. Stubs are used commonly as placeholders for implementation of a known interface, where the interface is finalized/known but the implementation is not yet known/finalized. The stub contains just enough code to allow it to be compiled and linked with the rest of the program.

Help is readily available for resolving compiler errors. Magdiel or Jonathan are available Sunday-Thursday evenings 7-10:00. They both have completed CPTR 314 and are familiar with C++. If they cannot help you or you need help with compiler errors at other times, send me the offending source code and I'll help you resolve the problem.
Run-time errors such as program exceptions (Visual C++) and segmentation faults (g++), are bad. While you genuinely may believe the problem lies in the compiler, your operating system, or your hardware, the problem is almost certainly somewhere in your code. If you cannot quickly locate the offending code, use a debugger. If you do not know how to use a debugger, see me and I'll show you how. Magdiel and Jonathan can assist as well.
For your safety, build your code with the highest warning levels provided by your compiler (/W4 for Visual C++, -Wall for g++). The warnings are generated for a reason. Do not be satisfied until your code compiles cleanly under the strictest scrutiny.
Unless otherwise specified, do not include any I/O (couts or cins) within code implementing collections such as lists, trees, etc.). Clients of your code are responsible for I/O. Any stray output from your implementation code may interfere with a testing framework used to evaluate your code for correctness and completeness.
Please include your name within a comment at the top of all source files you submit. This provides a nice check that the code I am grading is actually the person's code that I think it is. It also ensures that you will get the proper credit you're due.
Unless instructed otherwise, submit only the source files to eclass. I usually do not need an archive of all your development files.

CPTR 314 Data Structures, Algorithms, and Knowledge Systems Remarks on Assignments

CPTR 314
Data Structures, Algorithms,
and Knowledge Systems
Remarks on Assignments