Method overriding

Method overriding, in object oriented programming, is a language feature that allows a subclass or child class to provide a specific implementation of a method that is already provided by one of its superclasses or parent classes. The implementation in the subclass overrides (replaces) the implementation in the superclass by providing a method that has same name, same parameters or signature, and same return type as the method in the parent class.^[1] The version of a method that is executed will be determined by the object that is used to invoke it. If an object of a parent class is used to invoke the method, then the version in the parent class will be executed, but if an object of the subclass is used to invoke the method, then the version in the child class will be executed.^[2] Some languages allow a programmer to prevent a method from being overridden.

Language-specific examples

Ada

Ada provides method overriding by default. To favor early error detection (e.g. a misspelling), it is possible to specify when a method is expected to be actually overriding, or not. That will be checked by the compiler.

  type T is new Controlled with ......;
  procedure Op(Obj: in out T; Data: in Integer);
 
  type NT is new T with null record;
  overriding    -- overriding indicator
  procedure Op(Obj: in out NT; Data: in Integer);
  overriding    -- overriding indicator
  procedure Op(Obj: in out NT; Data: in String);
  -- ^ compiler issues an error: subprogram "Op" is not overriding

C#

C# does support method overriding, but only if explicitly requested using the modifiers override and virtual.

class abstract Animal {
  public          String name;
  // Methods
  public          void   drink();
  public virtual  void   eat();
  public          void   go();
}
 
class Cat : Animal {
  public new      String name;
  // Methods
  public          void   drink();  // warning: hides inherited drink(). Use new
  public override void   eat();    // overrides inherited eat().
  public new      void   go();     // hides inherited go().
}

When overriding one method with another, the signatures of the two methods must be identical (and with same visibility). In C#, class methods, indexers, properties and events can all be overridden.

Non-virtual or static methods cannot be overridden. The overridden base method must be virtual, abstract, or override.

In addition to the modifiers that are used for method overriding, C# allows the hiding of an inherited property or method. This is done using the same signature of a property or method but adding the modifier new in front of it.^[3]

In the above example, hiding causes the following:

Cat cat = new Cat();
 
cat.name = …;             // accesses Cat.name
cat.eat();                // calls Cat.eat()
cat.go();                 // calls Cat.go()
((Animal)cat).name = …;   // accesses Animal.name!
((Animal)cat).eat();      // calls Cat.eat()!
((Animal)cat).go();       // calls Animal.go()!

C++

In C++, the name of the parent or base class is used followed by the scope resolution operator to override functions. For example, the following code presents two classes, the base class Rectangle, and the derived class Box. Box overrides the Rectangle class's print() method, so as also to print its height.^[4]

#include <iostream>
 
class Rectangle {
public:
    explicit Rectangle(double l, double w) : length(l), width(w) {}
    virtual void print() const;
 
private:
    double length;
    double width;
};
 
void Rectangle::print() const { // print() method of base class
   std::cout << "Length = " << this->length << "; Width = " << this->width;
}
 
class Box : public Rectangle {
public:
    explicit Box(double l, double w, double h) : Rectangle(l, w), height(h) {}
    virtual void print() const; // virtual is optional here, but it is a good practice to remind it to the developer
 
private:
    double height;
};
 
void Box::print() const { // print() method of derived class
   Rectangle::print();  // Invoke parent print() method.
   std::cout << "; Height= " << this->height;
}

The method print() in class Box, by invoking the parent version of method print(), is also able to output the private variables length and width of the base class. Otherwise, these variables are inaccessible to Box.

The following statements will instantiate objects of type Rectangle and Box, and call their respective print() methods:

int main(int argc, char** argv) {
   Rectangle rectangle(5.0, 3.0);   rectangle.print();
   // outputs:
   // Length = 5.0; Width = 3.0
 
   Box box(6.0, 5.0, 4.0);
   // the pointer to the most overridden method in the vtable in on Box::print
   box.print(); // but this call does not illustrate overriding
   static_cast<Rectangle&>(box).print(); // this one does
   // outputs:
   // Length = 6.0; Width = 5.0; Height= 4.0
}

In C++11, similar to Java, a method that is declared final in the super class cannot be overridden; also, a method can be declared override to make the compiler check that it overrides a method in the base class.

Eiffel

In Eiffel, feature redefinition is analogous to method overriding in C++ and Java. Redefinition is one of three forms of feature adaptation classified as redeclaration. Redeclaration also covers effecting, in which an implementation is provided for a feature which was deferred (abstract) in the parent class, and undefinition, in which a feature that was effective (concrete) in the parent becomes deferred again in the heir class. When a feature is redefined, the feature name is kept by the heir class, but properties of the feature such as its signature, contract (respecting restrictions for preconditions and postconditions), and/or implementation will be different in the heir. If the original feature in the parent class, called the heir feature's precursor, is effective, then the redefined feature in the heir will be effective. If the precursor is deferred, the feature in the heir will be deferred.^[5]

The intent to redefine a feature, as message in the example below, must be explicitly declared in the inherit clause of the heir class.

class
    THOUGHT
feature
    message
            -- Display thought message
        do
            print ("I feel like I am diagonally parked in a parallel universe.%N")
        end
end
 
class
    ADVICE
inherit
    THOUGHT
        redefine
            message
        end
feature
    message
            -- <Precursor>
        do
            print ("Warning: Dates in calendar are closer than they appear.%N")
        end
end

In class ADVICE the feature message is given an implementation that differs from that of its precursor in class THOUGHT.

Consider a class which uses instances for both THOUGHT and ADVICE:

class
    APPLICATION
create
    make
feature 
    make
            -- Run application.
        do
            (create {THOUGHT}).message;
            (create {ADVICE}).message
        end
end

When instantiated, class APPLICATION produces the following output:

I feel like I am diagonally parked in a parallel universe.
Warning: Dates in calendar are closer than they appear.

Within a redefined feature, access to the feature's precursor can be gained by using the language keyword Precursor. Assume the implementation of {ADVICE}.message is altered as follows:

    message
            -- <Precursor>
        do
            print ("Warning: Dates in calendar are closer than they appear.%N")
            Precursor
        end

Invocation of the feature now includes the execution of {THOUGHT}.message, and produces the following output:

Warning: Dates in calendar are closer than they appear.
I feel like I am diagonally parked in a parallel universe.

Java

In Java, when a subclass contains a method that overrides a method of the superclass, it can also invoke the superclass method by using the keyword super (Lewis & Loftus, 2006).^[2] Example:

 class Thought {
    public void message() {
        System.out.println("I feel like I am diagonally parked in a parallel universe.");
    }
}
 
public class Advice extends Thought {
    @Override  // @Override annotation in Java 5 is optional but helpful.
    public void message() {
        System.out.println("Warning: Dates in calendar are closer than they appear.");
    }
}

Class Thought represents the superclass and implements a method call message(). The subclass called Advice inherits every method that could be in the Thought class. However, class Advice overrides the method message(), replacing its functionality from Thought.

Thought parking = new Thought();
parking.message();  // Prints "I feel like I am diagonally parked in a parallel universe."
 
Thought dates = new Advice();  // Polymorphism
dates.message();  // Prints "Warning: Dates in calendar are closer than they appear."

The super reference can be

public class Advice extends Thought {
      @Override
      public void message() {
          System.out.println("Warning: Dates in calendar are closer than they appear.");
          super.message();  // Invoke parent's version of method.
      }
  }

There are methods that a subclass cannot override. For example, in Java, a method that is declared final in the super class cannot be overridden. Methods that are declared private or static cannot be overridden either because they are implicitly final. It is also impossible for a class that is declared final to become a super class.^[6]

Python

In Python, when a subclass contains a method that overrides a method of the superclass, you can also call the superclass method by calling super(Subclass, self).method instead of self.method. Example:

class Thought(object):
    def __init__(self):
        pass
    def message(self):
        print "I feel like I am diagonally parked in a parallel universe."
 
class Advice(Thought):
    def __init__(self):
        super(Advice, self).__init__()
    def message(self):
        print "Warning: Dates in calendar are closer than they appear"
        super(Advice, self).message()

Notes

See also

• Implementation inheritance
• Inheritance semantics
• Method overloading
• Polymorphism in object-oriented programming
• Template method pattern
• Virtual inheritance

References

• Deitel, H. M & Deitel, P. J.(2001). Java How to Program (4th ed.). Upper Saddle River, NJ: Prentice Hall.
• Lewis, J. & Loftus, W. (2008). Java: Software Solutions (6th ed.). Boston, MA: Pearson Addison Wesley.
• Malik, D. S.(2006). C++ Programming: Program Design Including Data Structure. (3rd ed.). Washington, DC: Course Technology.
• Flanagan, David.(2002).Java in a Nutshell.Retrieved from http://oreilly.com/catalog/9780596002831/preview#preview
• Meyer, Bertrand (2009). Touch of Class: Learning to Program Well with Objects and Contracts. Springer.

External links

• Java Method Overriding by Hemanth Balaji
• Introduction to O.O.P. Concepts and More by Nirosh L.w.C.
• Overriding and Hiding Methods by Sun Microsystems