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.

An alternative solution is to have an interface instead of superclass.

The fragile base class problem has been blamed on open recursion (dynamic dispatch of methods on ), with the suggestion that invoking methods on   default to closed recursion (static dispatch, early binding) rather than open recursion (dynamic dispatch, late binding), only using open recursion when it is specifically requested; external calls (not using  ) would be dynamically dispatched as usual.

Java example
The following trivial example is written in the Java programming language and shows how a seemingly safe modification of a base class can cause an inheriting subclass to malfunction by entering an infinite recursion which will result in a stack overflow.

Calling the dynamically bound method inc2 on an instance of Sub will correctly increase the field counter by one. If however the code of the superclass is changed in the following way:

a call to the dynamically bound method inc2 on an instance of Sub will cause an infinite recursion between itself and the method inc1 of the super-class and eventually cause a stack overflow. This problem could have been avoided, by declaring the methods in the superclass as final, which would make it impossible for a sub-class to override them. However, this is not always desirable or possible. Therefore, it is good practice for super-classes to avoid changing calls to dynamically-bound methods.

Solutions

 * Objective-C has categories as well as non-fragile instance variables.
 * Component Pascal deprecates superclass calls.
 * Java, C++ (Since C++11) and D allow inheritance or overriding a class method to be prohibited by labeling a declaration of a class or method, respectively, with the keyword " ". In the book Effective Java, author Joshua Bloch writes (in item 17) that programmers should "Design and document for inheritance or else prohibit it".
 * C# and VB.NET like Java have " " and " " class declaration keywords to prohibit inheritance, and require a subclass to use keyword " " on overriding methods, the same solution later adopted by Scala.
 * Scala require a subclass to use keyword " " explicitly in order to override a parent class method. In the book "Programming in Scala, 2nd Edition", the author writes that (with modifications here) If there was no method f, the client’s original implementation of method f could not have had an override modifier. Once you add the f method to the second version of your library class, a recompile of the client code would give an compile error instead of wrong behavior.
 * In Kotlin classes and methods are final by default. To enable the class inheritance, the class should be marked with the  modifier. Likewise, a method should be marked as   to allow overriding of the method.
 * Julia allows only subtyping of abstract types and uses composition as an alternative to inheritance. It however has multiple dispatch.