COSC 072/503 Project 3

COSC 072/503: Computer Science II

Project 3
Spring 2008

Due: Wed, Mar 19 @ 5 PM
8 points

This project involves implementing a List ADT using a doubly-linked list.

I placed the class definitions for Node<T> and List<T> on seva, which you can retrieve with the commands:
```
seva% cd
seva% mkdir p3
seva% cd p3
seva% cp ~maloofm/cosc072/*.txt ./
```
This should copy list.txt and node.txt into the current directory, which you should use as the basis for list.h and node.h, respectively.
Implement the Node<T> class for doubly-linked nodes. You can just modify the Node<T> class from P2.
Use the doubly-linked Node<T> class to implement the List<T> class. Many methods from P2 are similar to those in List<T>. You could do some fancy stuff, but it is fine to move relevant code from P2 and modify it for List<T>.
Documentation: [ html | pdf ]
Test your implementation of the List<T> class in main.cc. However, we will use our own main function to evaluate your classes. Consequently, you must not modify the class names or the public interfaces. This would also be an important consideration for any large-scale software project. Our main.cc will include only main.h, so put all necessary includes there. That is, for this project, you must have all pertinent includes for main.cc in main.h. In general, you should not need to declare any additional methods or data members.

Instructions for Electronic Submission: At the top of the file main.cc (or the file containing the main function), place the following header comment, with the appropriate substitutions:

/*
 * COSC 072 Project 3
 * Name: <your name>
 * ID: <GoCard ID>
 * E-mail: <e-mail address>
 * Instructor: Maloof
 * TA: <TA's name>
 *
 * In accordance with the class policies and Georgetown's Honor Code,
 * I certify that, with the exceptions of the class resources and those
 * items noted below, I have neither given nor received any assistance
 * on this project.
 */

Instructions for Electronic Submission

If you need to include a message to your TA about your submission, then place the message in a file named README. Place the README file in the project's directory.

Assuming all of your code is in the subdirectory p3, directory, this directory and the submit program should be in the same directory:

seva% ls
p3/ submit.jar

To reduce the size of the zip file, before submitting, remove all object and executable files:

seva% cd p3
seva% make clean

If you need to include a message to your TA or me about your submission, then place the message in a file named README. Place the README file in the project's directory.

To move from the p3 directory to the parent directory, type

seva% cd ..

At this point, you should be above the p3 directory:

seva% ls
p3/ submit.jar

(Additional useful Unix commands)

When you are ready to submit, change the name of the directory to your netid. For example, if your netid is maloofm, then rename the directory p3 by typing

seva% mv p3 maloofm

Create a zip file of the directory and its contents by typing

seva% zip -r p3.zip maloofm/*

This command creates a zip file named p3.zip by recursively (-r) copying all of the files (*) from the directory maloofm/.

To submit the zip file type

seva% java -jar submit.jar -a p3 -f p3.zip

p3 is the name of the assignment (-a) and p3.zip is the file (-f) to be submitted for that assignment.

If the program submits the file successfully, you will receive a receipt by e-mail at the address <netid>@georgetown.edu.

Submit your project only once.

Once you've submitted your project, it is important to keep an electronic copy on a university machine (e.g., seva) that preserves the modification date and time. If we lose your project or the submission system breaks, then we will need to look at the modification date and time of your project to ensure that you submitted it before it was due.

You can also change the directory's name back to the original name. For example,

seva% mv maloofm p3

Note that changing the name of the directory does not change the dates of the files in the directory. You can also remove the zip file from your directory:

seva% rm p3.zip

The TA who will be grading your projects this semester is listed on the main page. You must submit your project before 5 PM on the due date.

Plan B

Submit is pretty reliable, but it is software. If you're running submit correctly and you see an error message labeled as SEVERE, then it's time to execute Plan B by using mail to submit your project.

To accomplish this, assuming the file you want to submit p3.zip, type at the seva prompt

seva% uuencode p3.zip p3.zip | mail cosc072@cush.georgetown.edu

Briefly, uuencode encodes the binary file p3.zip as an ASCII file that can be transmitted as mail. This form of the uuencode command pipes the ASCII-encoded file through standard input and into (|) the mail command.

When we receive you mail, we will save it to a file and use uudecode to translate the ASCII-encoded file back to the original binary file. Virtually all mail clients automatically encode binary files in this way.

Please don't use this account for communication. We don't check it regularly.