Avoiding obligatory SUPER constructor call
Posted: Tue May 12, 2020 3:28 pm
Is there any way to avoid calling SUPER constructor in a constructor of an inherited class?
There are situations when SUPER constructor is of totally different nature and simply may not be called and should be completely overriden.
I know, that's not very OOP-ish and one should use interface or something like that to untie that properly.
But. The question I'm asking is not just the point of mere interest but a, so to say, decision input, because refactoring price and changing OOP-model seem to be quite costly.
There are situations when SUPER constructor is of totally different nature and simply may not be called and should be completely overriden.
I know, that's not very OOP-ish and one should use interface or something like that to untie that properly.
But. The question I'm asking is not just the point of mere interest but a, so to say, decision input, because refactoring price and changing OOP-model seem to be quite costly.