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:
“Now launch the small ship, now as the body dies
and life departs, launch out, the fragile soul
in the fragile ship of courage, the ark of faith
with its store of food and little cooking pans
and change of clothes,”
—D.H. (David Herbert)
“I have always heard, Sancho, that doing good to base fellows is like throwing water into the sea.”
—Miguel De Cervantes (1547–1616)
“There might be a class of beings, human once, but now to humanity invisible, for whose scrutiny, and for whose refined appreciation of the beautiful, more especially than for our own, had been set in order by God the great landscape-garden of the whole earth.”
—Edgar Allan Poe (1809–1849)