Closed elfring closed 4 years ago
I don't think it's worth the effort on that class. The only public member which is worth of checking not nullptr
is PositionSolver
. Maybe a shared_ptr or a getter/setter for updating it and rising an exception in case of wrong set. However, I think it's better to delegate that on the caller (aka. TrackerWrapper and TrackerFactory).
On the other hand, I think the Client/
part would be worth to refactor a little bit. If you want to give it a try, it'll be welcome :)
I don't mind taking a look at the client part.
How do you think about to integrate any evolving software development approaches?
What do you specifically mean? @elfring
@rbroker published a software development approach which looks promising.
Would you like to wrap any pointer data members with the class template “std::unique_ptr”?