I've been asked to explain why it may be bad to have an abstract class that implements most of the methods (as an extreme case, only one abstract method) and has many sub-classes.Apart from having to look at a lot of code if you change the signature of that method I couldn't think of anything else. My answer didn't seem to satisfy the questioner.Is there any documented downside in using abstract classes this way?UPDATE: I'm changing the question's title to make it less opinion-based.
Is there any well known concern about having abstract class with few abstract methods?
abstract class