Project 2
Fall 2007
Due: Oct 11 @ 5 PM
6 points
Give tries a try. We'll talk about them in class. They're also discussed in Section 11.3 of the book. Your implementation of the Trie class must be complete, meaning that it should have a full (reasonable) set of constructors and methods.
The executable must read a filename from the command line, which contains a series of commands. P prints the strings stored in the trie, I inserts a string, R removes a string, and F determines whether a string is stored in the trie. Insert, remove, and find commands are followed by a string. An example of such a file follows:
I bear I bell I bid P I bully I buy I sell I stock I stop F pear F bull P R sell
You must provide a working Unix Makefile with your submission. Modify the Makefile from P1.
All class definitions and class methods must be documented with
DOC comments.
DOC comments for class definitions must include @author and @version
tags.
DOC comments for methods must include @param, @return, and @throw tags,
where appropriate.
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 modifications:
// // COSC 173 Project 2 // 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. //
Although you may use any C++ compiler to develop your program, it must run on seva, under Unix, and must compile using GNU g++. You must also provide a working UNIX Makefile for your project.
You'll be using the submit program to submit your assignments. To get the submit program, on seva, type
cp /home/maloofm/submit.jar ./
Copies of the submit program from previous semesters will not work, so get a fresh copy.
If you haven't already, place all of your code in a subdirectory named p2. To create this subdirectory, type
seva% mkdir p2To descend into the directory, type
seva% cd p2All of the files for your project should be in this directory. The submit program should be above this directory:
seva% ls .. p2/ submit.jar
If you need to include a message to the TA or me about your submission, then place the message in a file named README. Place the README file in the project's directory.
Before submitting, to reduce the size of the zip file, type 'make clean'.
To move up from the p2 directory, type
seva% cd ..You should be above the p2 directory:
seva% ls p2/ submit.jar
(Additional useful Unix commands)
When you're ready to submit, change the name of the directory to your netid. For example, if your netid is maloofm, then rename the directory p2 by typing
seva% mv p2 maloofmCreate a zip file of the directory and its contents by typing
seva% zip -r p2.zip maloofm/*This command creates a zip file named p2.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 p2 -f p2.zipp2 is the name of the assignment (-a) and p2.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 p2Note 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 p2.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.
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 p2.zip, type at the seva prompt
seva% uuencode p2.zip p2.zip | mail cosc173@cush.georgetown.eduBriefly, uuencode encodes the binary file p2.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.