3 ms·
> not as a way to model the problem domain ...unless your problem domain is a simulation of objects in a physical environment, in which case OO is well suited
by TuringTest 11y ago
> not as a way to model the problem domain
...unless your problem domain is a simulation of objects in a physical environment, in which case OO is well suited "as is".
But certainly, that's typically not your everyday scenario in development.
- adwn 11y agoAre you refering to simulations of physical phenomena? If so, then I disagree: You'll fare much better with large arrays of dumb structs, which enable immense performance improvements on today's computing architectures.
- TuringTest 11y agoIf you need to incorporate flexibility in the environment, with agents displaying lots of different behaviors (such as with video games), the large arrays of dumb structs will be much harder to organize. I agree that those structures are easier to make efficient, but for handling the hierarchy of different types of objects with different but related behaviors, you'll basically have to reimplement a limited form of object-orientation and message passing.