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)
“You see how this House of Commons has begun to verify all the ill prophecies that were made of it—low, vulgar, meddling with everything, assuming universal competency, and flattering every base passion—and sneering at everything noble refined and truly national. The direct tyranny will come on by and by, after it shall have gratified the multitude with the spoil and ruin of the old institutions of the land.”
—Samuel Taylor Coleridge (1772–1834)
“The intellectual is a middle-class product; if he is not born into the class he must soon insert himself into it, in order to exist. He is the fine nervous flower of the bourgeoisie.”
—Louise Bogan (1897–1970)