Assignment Turn-In

You may do two things with your assignment: submit it or test it. If you submit your assignment, the code you submit will be the basis for your grade on the assignment. If you test your assignment, the code you test will be deleted after the test is completed. Testing your code is not submitting it; you must explicitly submit your code at least once per assignment.

You may submit your assignment as many times as you want, up until the deadline for that assignment. After the deadline has passed, any further attempts to submit your assignment are rejected (without penalty) and your most recent submission is retained. If you have not submitted your assignment by the deadline, you may make a single submission (with penalty) after the deadline; any further attempts to submit after the deadline are rejected. You may test your assignment as many times as you want, whenever you want.

Your assignment must be sent from your Monmouth University account. The mailbox software uses various utilities to verify your identity (to the extent that your identity can be reliably verified with e-mail), and those utilities are usually unaccessible when e-mail is sent from outside the Monmouth domain. The mailbox software rejects any e-mail sent from an account it doesn't recognize as belonging to a class member.

where n is the number of the assignment you're turning in (1 <= n <= 7). You must be on a CS lab machine to access send-files.

Give the -t option to indicate you're testing your assignment; otherwise, give the -s option to indicate you're submitting your assignment. You must give one of -t or -s.

[ files . . . ] is an optional list of files. If a list of files is given on the command line, send-files will send all and only those files given. If no list of files is given on the command line, send-files will send all the C++ and include files it finds in the directory in which it was called. send-files assumes any file ending in the extension .cc, .C, .CC, or .cpp to be a C++ file and any file ending in .h to be an include file.

When you list files on the command line, you should list only those file found in the current directory; you should not list files found in subdirectories or the parent directory of the current directory.

If you list no files on the command line, send-files sends only the files it finds in the current directory, it will not look in other directories for files. Also, send-files will send all files it finds, so make sure the current directory contains only the files you want to send.

The five-minute response time only applies to your Monmouth University mailbox. If you forward your mail somewhere outside Monmouth, such as to Hotmail or Yahoo!, no response-time guarantees can be made, and it can take arbitrarily long to get your reply.

You indicate your group by including a file named "group" in your submission. The group file contains the Monmouth account ids of the members of your group; one of the ids will be yours, the other will be that of your partner. For example, if your account id is s000000 and your partner's is s999999, then the group file will contain

s000000 s999999

Every submission must include a group file; submissions without a group file will be rejected. If you don't want to join a group, the group file you include with your submission will contain only your account id.

Once you submit a group file, you must continue submitting the same group file. If you want to change your group - either by dropping a person, adding a person, or switching a person - you have to let me know so I can reset the group-tracking files.

For two-person groups, either group member may make submissions; if both group members make submissions, the most recent one will be taken as the official submission.

Test e-mail doesn't need a group file, so you may continue to test your code without forming a group. However, once you want to submit, you need to decide on your group.

You should receive a response within five minutes after sending your e-mail. If everything goes well, your response should look something like this:

From: rclayton@cslab00.monmouth.edu
Date: Wed, 5 Sep 2001 11:35:34 -0400 (EDT)
To: rclayton@monmouth.edu
Subject: Assignment 1 submit results.


$ date
Wed Sep  5 11:35:26 EDT 2001

$ ls
main.cc
tuple.cc
tuple.h

$ g++ -g -c -ansi -pedantic -Wall main.cc

$ g++ -g -c -ansi -pedantic -Wall tuple.cc

$ g++ -g -o count-tuples  main.o tuple.o

$

--

Your e-mail and this reply have been dealt with entirely by software
without human intervention.  You should not assume any person other
than yourself is aware of your e-mail or this reply; in particular, the
person who appears to have sent you this reply is completely unaware of
both your e-mail and this reply.

Keep the reply. The reply from your submission is your receipt; keep it. If there's any question about your assignment and you don't have the most recent reply, you're pretty much out of luck.

Don't fool around with the deadline. The clocks on the various CS lab machines are not well synchronized, and the clock on the machine receiving your submission is the only one that counts. Even though the clock on your machine shows 1:58 p.m., you may have already missed the deadline. Submit early and often.

The code you submit is the code that gets graded. You code is tested as submitted; I will not patch, replace, or change any software submitted to fix last-minute errors. I will not reset the deadline so you can resubmit an improved version of your code after the deadline. It is your responsibility to submit working code by the deadline.