• Task 1

  Resubmit Tokenizer.cpp and Tokenizer.h.

  Make sure it runs with the driver posted in P1/Secondary (in the posting account). The driver was updated the day after it was posted, since there was a period missing in Test 4. So make sure you used the latest driver. MovieQueue is not submitted.

  If you want split() to return an ArrayList, instead, write a new function called split2() which does that, and leave split() to return a vector as before. That way, we can run the same tests on your project.

• Task 2

  Only submit the latest Item.h and Item.cpp.

  Do NOT submit ItemSortedList nor ItemArrayList. They should not appear in your project (instead, you will submit SortedList and ArrayList).

• Task 3

  Submit SortedList and ArrayList (.cpp and .h).

  Also submit ItemComparator (.cpp and .h).

  Also, make sure that SortedList has two template variables: Data and Comparator and that locate() uses the Comparator object to do the comparison.

• Task 4

  Submit Algorithm (.cpp and .h).

• Task 5

  Submit MovieALQueue, MovieALQueueUnit (.cpp and .h)

  You do not have to submit Assert.h, TestCase.h, etc. We will use the files provided to you from P1.

  CORRECTION: Unfortunately, the files were meant to be added while grading your projects. However, they are not added during the submit process, which means you need to include the above files in your tarfile in order to properly produce MovieALQueueUnit.o.

• Task 6

  Any class files you write, plus their documentation. The documentation only needs brief descriptions of each method. You DO NOT NEED to write precondition, postcondition, nor running-time of any methods.

  Include a main.cpp where main() is implemented.

  Documentation should end in .mine.dcmt.

Makefile

• Use macros, please! We should see things like:

  CC = cxx
  LFLAGS = -w0 -std strict_ansi
  CFLAGS = -w0 -std strict_ansi -c
  

  at the top of your Makefile. Read the tutorial (click on Tutorial on main webpage) for an example (ignore the g++ related material).

• Your first target should be p2

• In order to make sure your Tokenizer, MovieALQueueUnit, MovieALQueue compiles, add Tokenizer.o, MovieALQueueUnit.o, MovieALQueue.o, to your dependencies for p2, but DON'T LINK THEM TO YOUR EXECUTABLE. Only link the .o files needed by p2.

  You need to have lines to compile each of these .o files with the -c options.

• So, when make p2 is called it creates the executable as well as Tokenizer.o, MovieALQueueUnit.o, MovieALQueue.o, which are not linked to the executable.

• If you haven't written these classes, then don't generate the .o files for them. Create only the ones that you wrote (which compile).

Reminders

• Did you reread FAQ, Game Clarifications, README.updates (in posting account)?
• Did you remove loops from SortedList.cpp?
• Does Item contain an ArrayList<std::string> which stores the name of the food?
• Does your program deal with case-insensitivity of commands, tags, name of food items, etc.?
• Did you rerun the token_driver from the posting account (P1/Secondary) on your Tokenizer class?
• Did you write a main.cpp?
• Did you test your files? (Make a temporary directory, copy your tar file, untar it, run make, copy the primary input and output, run it, save the output, diff the results, check to see only blank lines differ, before submitting it).
• Is your executable called p2?
• Did you modify SortedList.h by adding data members and/or public methods and/or change the constness of methods? You shouldn't have. Only private methods are allowed.
• Did you modify ArrayList.h by adding data members and/or public methods and/or change the constness of methods? You shouldn't have. Only private methods are allowed.
• Does your Makefile create .o files and LINK .o files?
• Did you avoid #include .cpp files except possible for template classes (not needed if you use the "cxx" method).
• Did you use SortedList<Item, ItemComparator> to store the food items on the board?
• Did you use ArrayList<Item> to store the food items from the player?
• Did you include documentation for classes you wrote?
• Did you include a README? Any information you wish to provide (such as whether you did extra credit unit testing, etc) should be noted.
• Did you name the class files you wrote with the .mine. (as in Foo.mine.cpp and Foo.mine.h for a class called Foo)?

See the class syllabus for policies concerning email Last Modified: Fri Sep 27 21:32:03 EDT 2002

Web Accessibility