TURN-IN Procedure for Project 1 (version 1.1, last modified 2/5 4:50pm)

1. Ensure that your project builds on ieng9 with your Makefile.  The 
   original Makefile or the one in the class public directory should suffice,
   unless you have done something strange.  You are responsible for ensuring
   that the Makefile that you provide properly compiles and sets up your
   compiler to run.  You might want to begin this part well in advance of
   the turn-in time.

   Note that your turnin must include an operational Makefile and oberon.csh
   file.

2. Make sure your testcases are in a subdirectory of your project source code.
   You are required to submit all your testcases.  You may also include any
   scripts, outputs, etc., that you use to run your testcases, but it is not
   required.

3. Run the TURNIN script in the class public directory.  The turn-in script
   should be run from inside your project directory.  Example (in project
   directory from your class account): ../../public/TURNIN

4. The turn-in script will prompt you for the required information (partner
   info), package your project, ensure it compiles, and run a minimal Oberon
   program, email your partners to notify them that you have turned in the
   project, and then turn in your project.  It will provide you with feedback as
   to what it is doing and give you several opportunities to abort the turn-in.
   The turn-in script can be run as many times as you like, although it is
   best if the same person runs it each time.

NOTES: Please insure that you are not turning in unnecessary files such
as backup tarballs and the likes as this will consume our quota for the
turn-in area unnecessarily.  Also be sure that you don't accidentally
leave out any files, or leave in debugging code.  Any code that prints
to standard output will be graded as compiler output.  Remember that each
mistake your turn-in will cost you 5% of your grade, and more if you have
to do something to fix the problem.

Thanks and Good Luck