How to do Rest of Project 2

• Copy your .cpp and .h files from Project 1 (Part 2) somewhere for Project 2.

• Write a Parser.cpp file based on Parser.h. You will need to copy you code from PlayerInputParser, DungeonParser, and TeamInputParser there. Change the names of the methods, so they match the ones in Parser.h.

• Redo your makefile so it works with Parser. Make sure it works on primary input and output.
• Write sort214. Unfortunately, in order to call it correctly, you need to specify the type. For example, the call sort214<Item> will sort an array list of Item. Leaving out the angle brackets and types seems to cause the compiler to complain. Don't know why.

  Debug this, make sure it sorts. Pick any sorting algorithm. Make sure it appears in your README file.

• At some point, you will need to convert PlayerList to Team. Team no longer has first or last pointers. Most of the code can be "removed" because you will be passing on the calls to SortedList. For example, if you have "add", it should look like:

      bool Team::add( const Player &player )
      {
         team.add( player );  // team is a SortedList object
      }
  

  Also, ask yourself if you really need copy constructors, assignment operators, and operator= (no, you don't).

  The only major change is to handle the new iterators. I would suggest writing methods called first, cfirst, etc. in Team and returning the corresponding iterators in SortedList. The alternative is to return the SortedList by reference (not a great idea, but oh well) and get the iterators directly.

• Since Team is new, you need to redo AllTeamsList to handle a vector of Team. (Eventually, to be replaced by an ArrayList of Team).

• Changing Team will cause a lot of other code to change. Most of this will probably occur in the parser that parses the teams, and the CommandParser.

• At each stage, try to compile, and get the primary input from P1 to work. In Parser, you may wish to have the various parses return back vectors (for now), and get those debugged, then switch them, one at a time to ArrayList.

• When you make all changes, then create a Robot class. It should basically be the same as Player (it may even be Player with a few changes). Look at the new project description, and see how to modify Robot.

• No, there isn't a Robot.h file. Create one.

Web Accessibility