University of Toronto - Spring 2001
Department of Computer Science

CSC 228: File Structures and Data Management
Instructor: Diane Horton

Packaging up Assignments


Your paper submission

Your TA may have other requirements. If so, follow them. For example, some TAs may have specifically said not to staple your work together. (And by the way, if you do use staples, make sure they do not prevent the TA from reading some parts of the page.)

Generally, you should think about the reader (your TA). Make it as easy as possible for them to read and assess your work.


Your electronic submission

What to submit

You must submit all your source code (including any additional code written only for the purposes of testing) and a makefile called "makefile". Your program should compile using plain old "make" with no arguments. For assignment 2, since we did not specify the interface to your program, make sure this is clearly explained in your report. You may also submit a README file that includes this information.

You do not have to submit object code, test input files, test output files, or your report.

How to submit it

To submit an individual file, say "blah.h" as part of assignment 1, use the command
        submit -N assnt2 csc228h blah.h 
You can also use a list of filenames, eg:
        submit -N assnt2 csc228h blah.h blah.cpp main.cpp
Or you can use wildcards, eg:
        submit -N assnt2 csc228h *.cpp *.h makefile
You may do multiple submit commands -- each one will just add more files into the submit directory where your code is stored for me. If you submit with the same filename twice, you must use the "-f" option to force submit to overwrite the old one.

See "man submit" if you need more details.


Deadlines

Both your electronic and paper submissions must be submitted by the deadline to count as on time.


Back to the St. George csc228 home page