Homework Submission Guidelines1

Jeffrey D. Oldham

2000 Mar 17

Revisions:

As mentioned in the syllabus, homework will be submitted via email. Please consider following these guidelines so our grading programs do not break on your code.

What to Submit

Your program's source code, submitted electronically, as described below. Every file must begin with the following:

If your program consists of multiple source files, submit a makefile to recreate your executable program by typing make. Makefiles will be discussed in class.

Always try to turn in something even if it's not completely correct or complete. Partial credit will be given when appropriate.

Submitting Programs via Email

To submit your program, e-mail its source code to the address corresponding to your section number: cs1321-1@cs.trinity.edu or cs1321-2@cs.trinity.edu.

To e-mail source code, use one of the following approaches.

If for some reason you submit a homework and then want to submit it again, just repeat the above procedure. I will grade only the most recent version I receive.

   
Automatic Reply to Homework Submission

After submitting homework to the appropriate email address, you should receive an automatic reply indicating the homework was received. This reply is sent to the computer used to submit your homework. For example, if you use a computer science computer to submit, the reply will be sent there.

To have all email sent to any computer science computer automatically forwarded to another account, use the following procedure:

1.
In your CS account's home directory, create a file called .forward, with exactly one line listing the email address where you want your email forwarded. This is probably your TUCC email address, e.g., Foo.Bar@trinity.edu.
2.
Make the file readable using chmod a+r .forward.

To check the contents of the file, type cat .forward.

How We Will Grade the Programs

We will grade the programs using one of the Trinity Computer Science machines available to you. (I believe the operating systems are all the same on all machines available to you.)

In particular, we will be compiling using commands like

g++ -Wall -pedantic foo.cc -o foo
These compilations should not produce any errors or warnings. (Warnings caused by incorrectly configured system files will be ignored, but I have run across very few of these.) Using the -Wall -pedantic options helps ensure your code is more likely to be portable to any machine.

Note that we will be grading using g++ on the Linux operating, not Visual C++.



Footnotes

... Guidelines1
©2000 Jeffrey D. Oldham . All rights reserved. This document may not be redistributed in any form without the express permission of the author.



2000-03-17