OOP Difference between Shadowing and Overriding
Introduction:
In this post, we will discuss the concept of Shadowing in OOP using c# and we will see how it works which will give you some idea that where we can use it and hopefully you will be able to decide when working practically in c# where it can be useful.What is Shadowing:
Shadowing is a concept of OOP (Object Oriented Programming) paradigm. Using Shadowing we can provide a new implementation to base class member without overriding it, which means that original implementation of base class member gets shadowed (hidden) with the new implementation of base class member provided in derived class.Consider a scenario where you have an external assembly which you have added in your project. You have a class in that assembly and it has a method which is not defined as virtual and you want to override that method(define your own implementation for that method) in the derived class. What would you do?
This is the scenario where you can use shadowing concept to override the method in the derived class
Definition:
Following are few definitions of itAccording to MSDN:
- Shadowing is concept of using Polymorphism in Object Oriented Programming. When two programming elements share the same name, one of them can hide, or shadow, the other one. In such a situation, the shadowed element is not available for reference; instead, when your code uses the element name, the compiler resolves it to the shadowing element.
- Shadowing is actually hiding overridden method implementation in derived class and call the parent call implementation using derived class object
Difference between Overriding and Shadowing
There is a major difference in shadowing and overriding which is
normally when we override a virtual method in derived class and create
instance of derived class and then if we hold reference to derived class
object as base class object, and call that member, it always calls derived class implementation which is supposed to happen, but in
shadowing the case is different, if for the same virtual member we
shadow it in the derived class using new keyword and we call the
implementation as above it will call base class implementation when we
have reference to object of type base class and if we have reference to
same object of derived type it will call derived type implementation so
base class and derived class implementation are hidden from each other,
method of which implementation to be called depends upon we are calling
the member using reference of base type or derived type.
Example:
Suppose, I have a base class BaseLogger which has two virtual methods(means they can be overridden in subclass) defined:
public abstract class BaseLogger
{
public virtual void Log(string message)
{
Console.WriteLine("Base: " + message);
}
public virtual void LogCompleted()
{
Console.WriteLine("Completed");
}
}
Now i create a class Logger that inherits from BaseLogger class. Logger class looks like this:
public class Logger : BaseLogger
{
public override void Log(string message)
{
Console.WriteLine(message);
}
public new void LogCompleted()
{
Console.WriteLine("Finished");
}
}
Now i want my Console to Print following lines:
Log started!
Base: Log Continuing
Completed
What should i write in Main Program to get the above output ? Here is the code we will need to write:
public class Program
{
public static void Main()
{
BaseLogger logger = new Logger();
logger.Log("Log started!");
logger.Log("Base: Log Continuing");
logger.LogCompleted();
}
}
The first call to Log method is OK, it has called Derived Logger class Log method and it should because we have overridden it in the Logger class.
The second call is also same.
Now note the third call, it has called the base class LogCompleted() method not derived class, it is because we have defined derived class method with new keyword which is hiding the derived class method when we are calling it with object of type BaseLogger which is our base class.
If we want to call the derived class LogCompleted() method our object reference should be of type Logger not BaseLogger.While in method overriding this is not the case.
In method overriding if we cast object of derived class to base class and call method, it will call overridden implementation of derived class.
