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

@CSharpIsGud Assuming you're talking about C# structs, that'll be worth keeping in the back of my mind, should I ever find myself debugging C# or learning the language.

Also, I presume the unnecessary new is because they aren't heap allocated, is C#'s new related to heap allocation at all?