Re:Game Development Essentials #1 - Don’t use inheritance fo...
by comex on Tuesday February 07, 2012 @01:35AM
(#3560733)
Even though the suggested model is ultimately much more flexible, I'm surprised the article didn't even mention multiple inheritance as the most obvious solution to the dialog/animated problem. Not all the world is Java.
[ Parent
| on HN ]
Re:Game Development Essentials #1 - Don’t use inheritance fo...
by WhaleBiologist on Tuesday February 07, 2012 @03:16AM
(#3560961)
Inheritance is usually the tightest form of coupling in a programming language. It is also usually misused horribly. A component/plugin architecture for game objects wins hands down.
Re:Game Development Essentials #1 - Don’t use inheritance fo...
by forrestthewoods on Tuesday February 07, 2012 @03:04AM
(#3560940)
Eek! Multiple inheritance is not implemented in most programming languages for good reason. In general it is wise to favor composition over inheritance.
Re:Game Development Essentials #1 - Don’t use inheritance fo...
by zura on Tuesday February 07, 2012 @04:33AM
(#3561149)
It is deciding between "IS A" and "HAS A".
In general, there is no such a rule that says: "HAS A" is wiser. It depends on the use case.