I'm learning C++ and Fortran, and I usually organize data with structs and put related functions in namespaces. What does object-oriented design add, and when is it worth using?
When do classes actually help instead of structs and functions?
Answers
In C++, a struct can have methods, constructors, private members, inheritance, and virtual functions just like a class. The main language difference is that struct members and base classes are public by default, while class members and base classes are private by default.
So the useful question isn't really which keyword you pick. It's whether you want the type to control how its state changes. A bank account type, for example, could keep its balance private and expose operations that enforce the rules you choose. That makes it harder for unrelated code to put the object into an invalid state.
Reply to this answer
Sometimes it's just convenient to keep the operations next to the data. If a type has state and several functions that naturally belong to it, methods give users a clear place to look for what they can do with an instance.
Your current approach can achieve much the same organization, though. A function that takes a struct as an argument isn't automatically worse than a method. Classes are a tool for making an interface clearer, not a guarantee of cleaner code.
Reply to this answer
Runtime polymorphism is another reason. Suppose code works with a common interface for several kinds of output. Different implementations can provide the same operations, and the calling code doesn't need a separate branch for each one.
That can make adding another implementation easier without changing the caller, provided the interface already supports what it needs. It also adds indirection and design overhead, so I wouldn't introduce a class hierarchy for a problem with only one straightforward behavior.
Reply to this answer
Stick with simple data and functions when that's clearer. Some behavior describes an interaction among several types, rather than something that naturally belongs to one object. Forcing it into a class can make those relationships harder to see.
Private state can be useful, but it can also get in the way when code needs to inspect or transform data in ways the original interface didn't anticipate.
Reply to this answer
Even if you rarely design classes yourself, you'll run into them in libraries. Containers and strings are examples of types that package data with operations, so understanding their interfaces is useful without making every part of your own program object-oriented.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_j64~fendavo.8:
So a struct with private data and methods can be object-oriented too?
_m42!queldavo.7:
Yes. In C++, the design matters more than whether you wrote struct or class.