EXPECT additional updates (including Makefile, and a few reminders before submitting).

You must submit the following files:

• Task 1

  StyleExercise.cpp after revision.

• Task 2

  Tokenizer.cpp and Tokenizer.h.

• Task 3

  MovieQueue.cpp, MovieQueue.h, MovieQueueUnit.cpp, MovieQueueUnit.h.

  In addition: Movie.cpp, Movie.h, Assert.h, AssertException.h, TestCase.h, TestSuite.h. (Check to make sure there aren't leftover files needed).

• Task 4

  ItemSortedList.dcmt (should include three classes: an outer class, and two nested ones).

  ItemArrayList.dcmt (should include three classes: an outer class, and two nested ones).

• Task 5

  Item.h, Item.cpp, ItemArrayList.h, ItemArrayList.cpp, ItemSortedList.h, ItemSortedList.cpp, ItemSortedListUnit.h, ItemSortedListUnit.cpp.

• 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.

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 p1

• In order to make sure your Tokenizer, MovieQueueUnit, MovieQueue, and ItemSortedListUnit compiles, add Tokenizer.o, MovieQueueUnit.o, MovieQueue.o, ItemSortedListUnit.o to your dependencies for p1, but DON'T LINK THEM TO YOUR EXECUTABLE. Only link the .o files needed by p1.

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

• So, when make p1 is called it creates the executable as well as Tokenizer.o, MovieQueueUnit.o, MovieQueue.o, ItemSortedListUnit.o.

• 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 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 p1?
• Did you modify ItemSortedList.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 ItemArrayList.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?
• Did you use ItemSortedList to store the food items on the board?
• Did you use ItemArrayList to store the food items from the player?
• Did you include documentation for classes you wrote?
• Did you include a README? It should indicate how you implemented locate (forward successor locate?), as well as which header files you wrote (i.e., the ones with .mine in the filename) which include ItemSortedList and ItemArrayList as data members, so we can see that they were used in the project correctly.
• 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