Using pointers as class data members often results in unexpected fun things when we copy such classes, e.g. double deletion or out-of-range errors for array members.
This is an issue for writing tests, and will probably be as well for implementing species interactions.
A solution would be a clearer management policy about these data members, as written in copy constructors, assignment operators, destructors etc.
TheoPannetier
commented
3 weeks ago
Using pointers as class data members often results in unexpected fun things when we copy such classes, e.g. double deletion or out-of-range errors for array members. This is an issue for writing tests, and will probably be as well for implementing species interactions.
A solution would be a clearer management policy about these data members, as written in copy constructors, assignment operators, destructors etc.