OOP Golden Rule

[Mr Flibble]

If nothing differentiates two object types (classes) except
the values of common (base class) properties and
behaviours then do not create a class for either.

Example: a weapon class is fine but a sword class
and a knife class are not as there are no intrinsic differences
between a knife and a sword.

This mirrors the OOA/D principle of preferring
object composition over class inheritance.

/Flibble

[Daniel]

On Tuesday, July 26, 2016 at 4:50:56 PM UTC-4, Mr Flibble wrote:
> If nothing differentiates two object types (classes) except
> the values of common (base class) properties and
> behaviours then do not create a class for either.
>
> Example: a weapon class is fine but a sword class
> and a knife class are not as there are no intrinsic differences
> between a knife and a sword.
>

It depends. Supposing the base class had an abstract method slashNeck, a derived
knife class might print "F**k!!!", while a derived sword class might print, well,
nothing. Generally the decision about whether a class is needed depends on purpose.

Daniel

[Mr Flibble]

"It depends" applies to most if not all generalizations. My
generalization is still a good rule of thumb. :)

/Flibble