FizzBuzz_generic_v1.cpp should be refactored into multiple classes

[jayjaybillings]

Right now FizzBuzz_generic_v1.cpp solves the generic FizzBuzz problem, but it would benefit from being written in an Object-Oriented way. For example, there are several obvious classes:

• FizzBuzzInput - A class that pulls the properties for the program from input and moves lines 22-42 into a separate class. This class would probably include the code for strRead too.
• Logger - A class that logs the output of the program instead of writing directly to the file as in lines 46-57.
• FizzBuzzEngine - A class that takes the input and the log and does the actual checking of the integers.
• FizzBuzzController - A class that takes input arguments from main, uses these arguments to create the logger, input, and engine, and finally executes everything.
• The current executable that you have with a main() function.

See @cruziken's example for reference.

[jayjaybillings]

When you do this, be sure that you don't put "using namespace std;" in any header files. It is OK to use this in main or an implementation (.cpp) file, but in headers using a namespace is discouraged.

(N.B. - I still make this mistake all the time when I write a header file!)

[jayjaybillings]

@dgquvn I noticed that the FizzBuzz branch does most of this renaming. However, the names are not ideal. For example, it is generally bad practice to name a class generate_output. That is a great name for a function, but you would name the class OutputGenerator. Likewise, writing_to_file would be FileWriter.