Learning C# and OOP, Polymorphism Based on Overloaded Methods
Baldwin explains the use of overloaded methods for the purpose of achieving compile-time polymorphism.
Published: November 4, 2002
C# Programming Notes # 112
This lesson is one of a series of lessons designed to teach you about the essence of Object-Oriented Programming (OOP) using C#.
The first lesson in the group was entitled Learning C# and OOP, Getting Started, Objects and Encapsulation. That lesson, and each of the lessons following that one, has provided explanations of certain aspects of the essence of Object-Oriented Programming using C#. The previous lesson was entitled Learning C# and OOP, Inheritance.
Necessary and significant aspects
This miniseries will describe and discuss the necessary and significant aspects of OOP using C#.
If you have a general understanding of computer programming, you should be able to read and understand the lessons in this miniseries, even if you don't have a strong background in the C# programming language.
You may find it useful to open another copy of this lesson in a separate browser window. That will make it easier for you to scroll back and forth among the different listings while you are reading about them.
I recommend that you also study the other lessons in my extensive collection of online programming tutorials. You will find a consolidated index at www.DickBaldwin.com.
Previous lessons introduced overloading and overriding methods, but didn't provide a lot of details. This lesson concentrates on the use of method overloading to achieve compile-time polymorphism.
The class named Object
Every class in C# is a direct or indirect subclass of the class named Object. Methods defined in the class named Object are inherited into all other classes. Some of those inherited methods may be overridden to make their behavior more appropriate for objects instantiated from the new subclasses.
Multiple methods with the same name
Overloaded methods have the same name and different formal argument lists. They may or may not have the same return type.
Polymorphism manifests itself in C# in the form of multiple methods having the same name. This lesson concentrates on method overloading, sometimes referred to as compile-time polymorphism. Subsequent lessons concentrate on method overriding, sometimes referred to as runtime polymorphism.
Overloaded methods may all be defined in the same class, or may be defined in different classes as long as those classes have a superclass-subclass relationship.
In an earlier lesson, I explained that most books on OOP will tell you that in order to understand OOP, you must understand the following three concepts:
I agree with that assessment.
Encapsulation and inheritance
Previous lessons in this series have explained Encapsulation and Inheritance. This lesson will tackle the somewhat more complex topic of Polymorphism.
Overloading and overriding methods
In the lessons on inheritance, you learned a little about overloading and overriding methods (you will learn more about these concepts as you progress through these lessons). This lesson concentrates on the use of overloaded methods to achieve compile-time polymorphism.
The sample programs that I used in the previous lessons in this series dealt with two kinds of car radios:
I couched those programs in a real-world scenario in an attempt to convince you that encapsulation and inheritance really do have a place in the real world.
Programs were fairly long
However, even though those programs were simple in concept, they were relatively long. This made them somewhat difficult to explain due simply to the amount of code involved.
Keep it short and simple
At this point, I am going to back away from real-world scenarios and begin using sample programs that are as short and as simple as I know how to make them, while still illustrating the important points regarding polymorphism. My objective is to make the polymorphic concepts as clear as possible without having those concepts clouded by other programming issues.
I will simply ask you to trust me when I tell you that polymorphism has enormous application in the real world.
Every class extends some other class
There is another aspect of inheritance that I didn't explain in the previous lessons in this series.
Every class in C# extends some other class. If you don't explicitly specify the class that your new class extends, it will automatically extend the class named Object.
A class hierarchy
Thus, all classes in C# exist in a class hierarchy where the class named Object forms the root of the hierarchy.
Some classes extend Object directly, while other classes are subclasses of Object further down the hierarchy (they extend classes, which extend classes, which extend Object).
Methods in the Object class
The class named Object defines default versions of the following methods:
Some of the methods in this list are defined in overloaded versions in the Object class (same name, different formal argument lists).
Every class inherits these methods
Because every class is either a direct or indirect subclass of Object, every class in C#, (including new classes that you define), inherit these methods.
To be overridden ...
Some of these methods are intended to be overridden for various purposes. This includes Equals, Finalize, GetHashCode, and ToString.
However, some of them, such as GetType, are intended to be used directly without overriding.
What is polymorphism?
The meaning of the word polymorphism is something like one name, many forms.
How does C# implement polymorphism?
Polymorphism manifests itself in C# in the form of multiple methods having the same name.
In some cases, multiple methods have the same name, but have different formal argument lists (overloaded methods).
In other cases, multiple methods have the same name, same return type, and same formal argument list (overridden methods).
Three distinct forms of polymorphism
From a practical programming viewpoint, polymorphism manifests itself in three distinct forms in C#:
I will begin the discussion of polymorphism with method overloading, which is the simplest of the three. I will cover method overloading in this lesson and will cover polymorphism based on overridden methods using inheritance and interfaces in subsequent lessons.
Method overloading versus method overriding
Don't confuse method overloading with method overriding.
C# allows you to have two or more method definitions in the same scope with the same name, provided that they have different formal argument lists.
Some authors refer to method overloading as a form of compile-time polymorphism, as distinguished from run-time polymorphism.
This distinction comes from the fact that, for each method invocation, the compiler determines which method (from a group of overloaded methods) will be executed. This decision is made when the program is compiled.
Selection based on the argument list
In practice, the compiler simply examines the types, number, and order of the parameters being passed in a method invocation, and selects the overloaded method having a matching formal argument list.
A sample program
I will discuss a sample program named Poly01 to illustrate method overloading. A complete listing of the program can be viewed in Listing 4 near the end of the lesson.
Within the class and the hierarchy
Method overloading can occur both within a class definition, and vertically within the class inheritance hierarchy.
The program named Poly01 illustrates both aspects of method overloading.
Class B extends class A, which extends Object
Upon examination of the program, you will see that the class named A extends the class named Object. You will also see that the class named B extends the class named A.
The class named Poly01 is a driver class whose Main method exercises the methods defined in the classes named A and B.
Designed to illustrate method overloading
Once again, this program is not intended to correspond to any particular real-world scenario. Rather, it is a very simple program designed specifically to illustrate method overloading.
Will discuss in fragments
As is my usual approach, I will discuss this program in fragments.
The code in Listing 1 defines the class named A, which explicitly
Recall that explicitly extending Object is not required (but it also doesn't hurt anything).
By default, the class named A would extend the class named Object automatically, unless the class named A explicitly extends some other class.
The method named m()
The code in Listing 1 defines a method named m(). Note that this version of the method has an empty argument list (it doesn't receive any parameters when it is executed). The behavior of the method is simply to display a message indicating that it has been invoked.
The class named B
Listing 2 contains the definition for the class named B.
The class named B extends the class named A, and inherits
the method named m defined in the class named A.
In addition to the inherited method named m, the class named B defines two additional overloaded versions of the method named m:
(Note that each of these two versions of the method receives a single parameter, and the type of the parameter is different in each case.)
As with the version of the method having the same name defined in the class named A, the behavior of each of these two methods is simply to display a message indicating that it has been invoked.
The driver class
Listing 3 contains the definition of the driver class named Poly01.
Invoke all three overloaded methods
The code in the Main method
One version is inherited
Note that the overloaded version of the method named m, defined in the class named A, is inherited into the class named B. Hence, it can be invoked on a reference to an object instantiated from the class named B.
Two versions defined in class B
The other two versions of the method named m are defined in the class named B. Thus, they also can be invoked on a reference to an object instantiated from the class named B.
As you would expect from the code that you examined for each of the three methods, the output produced by sending messages to the object asking it to execute each of the three overloaded versions of the method named m is:
Parameters are not displayed
Note that the values of the parameters passed to the methods do not appear in the output. Rather, in this program, the parameters are used solely to make it possible for the compiler to select the correct version of the overloaded method to execute in each case.
This output confirms that each overloaded version of the method was properly selected for execution based on the matching of method parameters to the formal argument list of each method.
Previous lessons introduced overloading and overriding methods. This lesson concentrates on the use of method overloading to achieve compile-time polymorphism.
All classes in C# form a hierarchy with a class named Object at the root of the hierarchy. Thus, every class in C# is a direct or indirect subclass of the class named Object.
If a new class doesn't explicitly extend some other class, it will, by default, automatically extend the class named Object.
The Object class defines default versions of several different methods. These methods are inherited into all other classes. Some of the inherited methods may be overridden to make their behavior more appropriate for objects instantiated from the subclass.
Overloaded methods have the same name and different formal argument lists. They may or may not have the same return type.
The word polymorphism means something like one name, many forms. Polymorphism manifests itself in C# in the form of multiple methods having the same name.
Polymorphism manifests itself in three distinct forms in C#:
This lesson concentrates on method overloading, sometimes referred to as compile-time polymorphism. This form of polymorphism is distinguished by the fact that the compiler selects among a group of overloaded methods on the basis of the types and the number of parameters passed to the method when it is invoked. The selection is made when the program is compiled (rather than being made later when the program is run).
Overloaded methods may all be defined in the same class, or may be defined in different classes as long as those classes have a superclass-subclass relationship in the class hierarchy.
The sample program in this lesson illustrates three overloaded versions of the same method name with two of the versions being defined in a single class, and the other version being defined in the superclass of that class.
The next lesson teaches you about assignment compatibility, type conversion, and casting for both primitive and reference types. It also teaches you about the relationship between reference types, method invocations, and the location in the class hierarchy where a method is defined.
A complete listing of the program is shown in Listing 4 below.
Copyright 2002, Richard G. Baldwin. Reproduction in whole or in part in any form or medium without express written permission from Richard Baldwin is prohibited.
Richard Baldwin is a college professor (at Austin Community College in Austin, Texas) and private consultant whose primary focus is a combination of Java, C#, and XML. In addition to the many platform and/or language independent benefits of Java and C# applications, he believes that a combination of Java, C#, and XML will become the primary driving force in the delivery of structured information on the Web.
Richard has participated in numerous consulting projects and he frequently provides onsite training at the high-tech companies located in and around Austin, Texas. He is the author of Baldwin's Programming Tutorials, which has gained a worldwide following among experienced and aspiring programmers. He has also published articles in JavaPro magazine.
Richard holds an MSEE degree from Southern Methodist University and has many years of experience in the application of computer technology to real-world problems.
© 1996, 1997, 1998, 1999, 2000, 2001, 2002 Richard G. Baldwin