mlposey / genetics-sim Goto Github PK

Most objects that are created by Factory classes are copied at least once in transit to their final destination. It may be better to create shared_ptr objects that store pointers to these.

In v2.0, the mating logic incorporates the chromosomal crossover process. This should be implemented in a new mating method.

The v2.0 specification requires different metrics to be stored and eventually output to the screen. These should be captured during the mating process and stored in an efficient way while awaiting the end of the simulation.

There are inconsistencies across the code base such as:
1.) Mismatched tabs/spaces
2.) No standard for tab lengths when using methods with multiple arguments
3.) No standard for declaring multiple variables of the same type on consecutive lines. Should the type be re-declared or should commas be used? When should a newline be introduced if using commas?

The old output was stripped due to major v2.0 structural changes. An output system should be used that models that which is found in the instructor exe output.