What design pattern should I use for specific multiple inheritance?

Let's say I have an interface called Squid.

And we have a bunch of different types of squids:

Here's everything a squid can be:


How would I go about create an instance of a squid? Should I go about creating 4 classes BasicAquaticSquid, BasicLandSquid, AdvancedAquaticSquid, AdvancedLandSquid like this:

I think that's called the Abstract Factory method? It seems very tedious though. Any better way of doing so?


You are viewing a single comment. View All
Answered by xxpertHacker [earned 5 cycles]
View Answer

@xxpertHacker The main difference are the functions. Each class has it's own unique set of functions. For example AquaticSquid has Swim(), Drown(), and Float(). I'll try to reduce the number of functions I have, but for the time being, each class has it's own funtcions.