Fragile Base Class
The fragile base class problem is a fundamental architectural problem of object-oriented programming systems where base classes (superclasses) are considered "fragile" because seemingly safe modifications to a base class, when inherited by the derived classes, may cause the derived classes to malfunction. The programmer cannot determine whether a base class change is safe simply by examining in isolation the methods of the base class.
One possible solution is to make instance variables private to their defining class and force subclasses to use accessors to modify superclass states. A language could also make it so that subclasses can control which inherited methods are exposed publicly. These changes prevent subclasses from relying on implementation details of superclasses and allow subclasses to expose only those superclass methods that are applicable to themselves.
Another alternative solution could be to have an interface instead of superclass.
Read more about Fragile Base Class: Solutions
Famous quotes containing the words fragile, base and/or class:
“Parents need all the help they can get. The strongest as well as the most fragile family requires a vital network of social supports.”
—Bernice Weissbourd (20th century)
“I think it is worse to be poor in mind than in purse, to be stunted and belittled in soul, made a coward, made a liar, made mean and slavish, accustomed to fawn and prevaricate, and “manage” by base arts a husband or a father,—I think this is worse than to be kicked with hobnailed shoes.”
—Frances Power Cobbe (1822–1904)
“Money couldn’t buy friends, but you got a better class of enemy.”
—Spike Milligan (b. 1918)