Objectives

• to use inheritance and polymorphism
• (CS527) to use the factory pattern

Assignment

The behavior of the Game program should be the same as the SpinOut and Conway programs, accounting for the additional command-line argument to determine which game to play and for the repositioned -i argument, and except as noted below.

• Reading moves from streams is no longer line-based. Instead, read the next int from the stream for SpinOut and the next four ints from the stream, separated by whitespace, for Conway's Soldiers.
• There is a line break in the "illegal move" message after "for".
• Each line of output for the Conway's Soldiers board should end in a newline character; when std::endl is output after the board then there will be a blank line in the output.

Your solution should follow good object-oriented design. (So use inheritance and declare members in the base class where it makes sense to do so. Don't create one class that implements both games.)

The constructors for Conway should still work, as should the assignment operators when the object assigned to is of static type Conway.

(CS527) Make sure your makefile compiles main with the -DCS527 option to select the code that creates the Game objects using a factory. The factory may throw exceptions when used to create a game initialized from a source the game does not support (from a file for SpinOut and from a string for Conway's Soldiers).

(CS527) The version of Game compiled without the -DCS527 option should work as well.

We also reserve the right to deduct points from submissions for violations of the following guidelines.

• Submissions should not rely on any particular compiler's implementation in situations where the C++ specification states that behavior is undefined.
• Submissions should not leak memory.
• All source code should be easily comprehended, with adequate and consistent spacing, concise but descriptive idenitifiers, comments before long sequences of code, and enumerations and constants favored over literals.
• Submissions should be modularized, with collections of related functions and methods divided into separate files. Generally this means that each class that is intended for external use should have its own header and implementation files declaring and defining its members and related functions.
• Header files should be written so that they can be #included regardless of what other files have been #included -- if a declaration is required by your header files, then #include the appropriate header file in your header file (or write a forward declaration in your header) rather than relying on your #includers to have already #included those header files before they #include yours.
• You should use C++ libraries and constructs rather than the corresponding C libraries and constructs where possible and not otherwise specified (for example, use cin and cout with the I/O operators << and >> rather than printf and scanf).
• Each public member of a class should be documented with a comment before it in the header file. For a method the comment should include 1) a description of the parameters including any limitations on the values allowed (preconditions), and 2) a description of what the function does and/or what it returns (postconditions).
• Things that make sense to be declared as const should be declared as const.
• There should be no warnings when your code is compiled with the -Wall and -pedantic options.

File and Submissions

• game_main.cpp (don't change)

Submit everything you need in order to build Game, including the unchanged game_main.cpp.

Example

[jrg94@tick Game]$ ./Game spinout -i
///////
6
//////-
5
illegal move
4
////-/-
[jrg94@tick Game]$ ./Game spinout -s ------/ -i
------/
6
-------
1 moves
[jrg94@tick Game]$ ./Game spinout -s ------/ 6
SOLVED
[jrg94@tick Game]$ ./Game spinout 6 4 5
illegal move 5 in position 3 for
////-/-
[jrg94@tick Game]$ ./Game spinout 6 4 6 5 6
////---
[jrg94@tick Game]$ ./Game conway -i
......
......
.XXX..
...X..
......

3 3 1 3
......
...X..
.XX...
......
......

1 3 0 3
illegal move
2 1 2 3
......
...X..
...X..
......
......

[jrg94@tick Game]$ ./Game conway -f conway_2.in -i
...
.X.
.X.

2 1 0 1
.X.
...
...

1 moves
[jrg94@tick Game]$ ./Game conway 3 3 1 3  2 1 2 3  2 3 0 3
SOLVED
[jrg94@tick Game]$ ./Game conway 3 3 1 3  1 3 0 3  2 1 2 3  2 3 2 1
illegal move 1 3 0 3 in position 2 for
......
...X..
.XX...
......
......

[jrg94@tick Game]$ ./Game conway -f conway_21.in 5 4 3 4  5 2 5 4
.........
.........
.........
....X....
..XX.XX..
....XXX..
..XXXXX..
..XXXXX..
....X....

Where conway_2.in contains

3 3
...
.X.
.X.

9 9
.........
.........
.........
.........
..XXXXX..
..XXXXX..
..XXXXX..
..XXXXX..
....X....