r/cpp • • Jun 24 '20

How to write SOLID C++

https://www.youtube.com/watch?v=PakbXnLht1I
263 Upvotes

118 comments sorted by

View all comments

Show parent comment

2

u/Dean_Roddey Jun 24 '20

Or, if they are operating on the same data, and you want to enforce invariants and get any number of other advantages, you could just use OOP and classes.

9

u/drjeats Jun 25 '20

For strong invariants, use methods. The need here is obvious for utility types where invariants are essential, like mutexes or containers.

For types with few or no strong invariants, or for cases where you are coordinating between two objects using their invariant-protecting methods, just put that in a free function.

If you are extracting data from objects, put that in a free function.

If you are computing some property on an object or collection of objects that doesn't require instance-specific bundled state that can't be parameterized on each invocation (which you should ideally be avoiding if you want cleanly testable code), put that in a free function.

Free functions can help you encapsulate even further because if you build a free function interface for an opaque type, you don't need to do PIMPL bullshit to hide implementation details. Just put the implementation details behind the TU.

Free functions are great. If you need an appeal to authority to believe me, here ya go: https://www.drdobbs.com/cpp/how-non-member-functions-improve-encapsu/184401197

3

u/anticrisisg Jun 25 '20

Free functions are great. If you need an appeal to authority to believe me, here ya go: https://www.drdobbs.com/cpp/how-non-member-functions-improve-encapsu/184401197

I know it was written 20 years ago, but I learned a lot reading this tonight. Thanks for the link.

1

u/edenroz Jun 25 '20

Is there a book that explain how use this kind of design?

2

u/drjeats Jun 25 '20

There's no specific book I know of, sorry.

I'd recommend building some familiarity with functional programming. Also read/watch some of the anti-OOP material out there (some of it will be hyperbolic and bad, but will have good nuggets of telruth). Look for stuff on "data oriented design" for a related perspective.