Submission Guidelines

Last Revised: Feb. 1, 2015

Standard Deliverables:

Throughout the semester, programs with documentation will be due at class time. In order to submit your code, I expect the following things to be submitted using the cssubmit command (detailed below):

• • All of the files needed to do a test run of your code. Since I want each class definition to be placed in its own header file, you will have a .h and a .cpp for each class.

  • A makefile (when requested) which compiles your code.

  • Submit all the above files (source files, data files, makefile) and NOT executables, core dumps, etc. Core dumps should be submitted to county dumps.

Submitting Your Files

Submission is easy. You are to develop your projects in their own directories. So, for program #4, you will have a directory in your DFS account called h4 or hw4 or prog_4 or whatever you think appropriate. There should be NO files in that directory not pertaining to assignment #4. On one of the machines named below (and from no other!), enter the command:

cssubmit 5201 a X, where X is an integer designating which assignment you are submitting for

For example, if you are submitting your assignment #4 code, you enter:

cssubmit 5201 a 4

and this script will ftp all the files in the current working directory (presumably your assignment #4 directory) to another directory where it will be graded

Like I said, it's easy.

Words of Caution

Develop your software on the dell machines so named: rc01xcs213.managed.mst.edu -> rc32xcs213.managed.mst.edu.

Be sure you are using the g++ compiler in /usr/bin/. You can determine this with the command which g++. If it says /usr/testbin/g++ you are using an untested, unstable compiler.