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 itself.
Also, in general, programmers should program to interfaces rather than concrete implementations.
US Patent Issued to Microsoft on April 16 for "Selectively Exposing Base Class Libraries Based on Application Execution Context" (Indian Inventors)
Apr 16, 2013; ALEXANDRIA, Va., April 16 -- United States Patent no. 8,424,107, issued on April 16, was assigned to Microsoft Corp. (Redmond,...
Contract Notice: Department of the Army (APO) Issues Solicitation for "Log Base Class II & Class IV Supply Items"
Oct 27, 2010; WASHINGTON, Oct. 27 -- Department of the Army, Army Contracting Command has a requirement for "Log Base Class II & Class IV...