Corrections/Modifications

• 4/5: Called the file "Second.cpp", as per project description
• 4/4: Added PairComparator

Checklist

• Did you make sure to submit the following files?
  • Makefile
  • README
  • main.cpp (just calls run() -- see below)
  • run.cpp and run.h
  • TreeExercise.answers (Task 1)
  • Review.txt (Task 9)
  • InputTokenizer.cpp and InputTokenizer.h
  • SimpleMap.cpp and SimpleMap.h
  • Movie.cpp and Movie.h
  • SortedList.cpp and SortedList.h
  • ArrayList.cpp and ArrayList.h
  • BstSortedList.cpp and BstSortedList.h
  • BstSortedList.doc
  • BstMap.cpp and BstMap.h (EXTRA CREDIT)
  • Pair.cpp and Pair.h (EXTRA CREDIT)
  • PairComparator.cpp and PairComparator.h (EXTRA CREDIT)
  • Second.cpp
  • Various files with the proposal
  • MovieTester.cpp and MovieTester.h
  • MovieSortedListTester.cpp and MovieSortedListTester.h
  • MovieArrayListTester.cpp and MovieArrayListTester.h
  • MovieBstSortedListTester.cpp and MovieBstSortedListTester.h (NEW!)
  • Algorithm.cpp and Algorithm.h
  • MovieComparator.cpp and MovieComparator.h

• Notice that the file for the tester is called MovieBstSortedListTester.cpp and MovieBstSortedListTester.h. However, the actual tester class can be called anything (for example, MBSLTester). We won't be testing your class separately (i.e., with our own drivers). SO, even though the class may be called MBSLTester, place it in files called MovieBstSortedListTester.cpp and MovieBstSortedListTester.h.

• main.cpp should be VERY simple. It should basically be:

  #include "run.h"
  
  int main()
  {
     run() ;
     return 0 ;
  }
  

  run.h should be fairly simple too:

  #ifndef RUN_H
  #define RUN_H
  
  void run() ;  // prototype
  
  #endif
  

  In run.cpp, you will have a function called run() which contains all the code that used to appear in main(). Any helper functions used by main() should now appear in run.cpp.

• Did you write BstSortedList.doc? This should be mostly a cut-and-paste from SortedList.doc, plus any additional methods you may have written.

• Did you write a file called Foo.myclass.doc for two classes? (Task 8 and 9) (where Foo is replaced by the name of the two classes)?

• Did you implement one class? Did you write Foo.driver.output, Foo.h, and Second.cpp (with just runTestDriver() code) for a second class? (where Foo is replaced by the name of the class you used).

• Did you fill out the README? The directions are in the posting account under README.directions and you should copy the file README and answer the FOUR questions in it.

• Did you include BstMap.cpp and BstMap.h for extra credit? You must also include Pair.cpp and Pair.h too. You need to submit this with your entire project if you want extra credit. It can't be submitted separately. We grade a single project submission. (You do not have to write BstMap.doc, but you should comment the file).

• Did you make sure your Makefile produces the executable p3? Does it use constants (macros) as mentioned in Task 0? (You won't be counted off in previous projects, but you were supposed to use them---even back in CMSC 114).

• Did you write a static method called void runTestDriver() for BstSortedList? Make sure it appears as the first method of BstSortedList.cpp (at the top) so TAs can find it easily.

• Did you make sure you have recent files from the P3 directory and read updates from the FAQ, Project description, and posting account?

• Did you make sure to test your files (make sure that it untars correctly, etc)? Just because it "submits" doesn't always mean that you have passed primary (although it USUALLY means that). It's best to test your own tar file, and run diff (as explained in the handout given in the first day of lab).

• Did you reread the FAQ?

• Did you alter the parameters to public functions in BstSortedList? You shouldn't have. In general, AVOID CHANGING PUBLIC methods. Some people change parameters when it becomes inconvenient, even though in reality, altering public methods may mean other people who use your code will be very unhappy, and while no one else is expected to use your code, the best way to rewrite recursive functions is to use private helpers function which does all the recursion, and pass in the parameters you want.

See the class syllabus for policies concerning email Last Modified: Thu Apr 4 01:22:22 EST 2002

Web Accessibility