Polymorphism


What is Polymorphism?

Polymorphism means one name many forms.

Polymorphism means one object behaving as multiple forms.
One function behaves different forms.
In other words, "Many forms of a single object is called Polymorphism."

Real World Example of Polymorphism:
Example-1: 
A Teacher behaves to student.
A Teacher behaves to his/her seniors.
Here teacher is an object but attitude is different in different situation.
Example-2: 
Person behaves SON in house at the same time that person behaves EMPLOYEE in office.
Example-3: 
Your mobile phone, one name but many forms
  • As phone
  • As camera
  • As mp3 player
  • As radio
With polymorphism, the same method or property can perform different actions depending on the run-time type of the instance that invokes it. 


There are two types of polymorphism:-

1)  Static or Compile time Polymorphism
2)  Dynamic or Runtime Polymorphism.

Static or Compile time Polymorphism:-
·   In Static Polymorphism the decision is made at compile time.
      ·   Which method is to be called is decided at compile-time only ?
      ·   Method overloading is an example of this.
 ·   Compile time polymorphism is method overloading, where the compiler knows which             overloaded method it is going to call.

Method overloading is a concept where a class can have more than one method with same name and different parameters. 
Compiler checks the type and number of parameters passed on to the method and decides which method to call at the compile time and it will give an error if there are no method that matches the method signature of the method that is called at the compile time.
      
      Example:-

              
namespace MethodOverloadingBysatyasingh
{
    class Program
    {
        public class TestOverloading
        {

            public void Add(string a1, string a2)    
            {
                Console.WriteLine("Adding Two String :" + a1 + a2);
            }

            public void Add(int a1, int a2)
            {
                Console.WriteLine("Adding Two Integer :" +  a1 + a2);
            }

        }

        static void Main(string[] args)
        {
            TestOverloading obj = new TestOverloading();

            obj.Add("Manish " , "Agrahari");

            obj.Add(5, 10);

            Console.ReadLine();
        }
    }
}

 Dynamic or Runtime Polymorphism:-

Run-time polymorphism is achieved by method overriding.

Method Overriding allows us to have methods in the base and derived classes with same name and same parameters.

By runtime polymorphism we can point to any derived class from the object of the base class at runtime that shows the ability of runtime binding.

Through the reference variable of a base class, the determination of the method to be called is based on the object being referred to by reference variable.

Compiler would not be aware of the method is available for overriding the functionality or not. So compiler would not give any error at compile time. At runtime it will be decided which method to call and if there is no method at runtime it will give an error

See Following Example:-
namespace PolymorphismBysatyasingh
{
    class Program
    {
        public class Base
        {

            public virtual void Show()
            {
                Console.WriteLine("Show From Base Class.");
            }
        }

        public class Derived : Base
        {
            public override void Show()
            {
                Console.WriteLine("Show From Derived Class.");
            }
        }
        static void Main(string[] args)
        {
            Base objBase;
            objBase = new Base();
            objBase.Show();//    Output ----> Show From Base Class.

            objBase = new Derived();
            objBase.Show();//Output--> Show From Derived Class.

            Console.ReadLine();
        }
    }
} 



Compiler demands virtual Show()  method and it compiles successfully. The right version of Show()  method cannot be determined until run-time since only at that time Base objBase is initialized as Derived.

Virtual Keyword:-
According to MSDN, “The virtual keyword is used to modify a method, property, indexer or event declaration, and allow it to be overridden in a derived class.”
Virtual Method:-
Virtual method is a method whose behavior can be overridden in derived class.
Virtual method allows declare a method in base class that can be redefined in each derived class.
 When a virtual method is invoked, the run-time type of the object is checked for an overriding member. The overriding member in the most derived class is called, which might be the original member, if no derived class has overridden the member.
  • By default, methods are non-virtual. You cannot override a non-virtual method.
  • You cannot use the virtual modifier with the static, abstract, private or override modifiers.
  • Virtual properties behave like abstract methods, except for the differences in declaration and invocation syntax.
  • It is an error to use the virtual modifier on a static property.
  • A virtual inherited property can be overridden in a derived class by including a property declaration that uses the override modifier.


 Virtual method solves the following problem:-
In OOP when a derived class inherits from a base class, an object of the derived class may be referred to (or cast) as either being the base class type or the derived class type. If there are base class methods overridden by the derived class, the method call behavior is ambiguous.
In C#, polymorphism is explicit - you must have a virtual (or abstract) modifier on the base class method (member) and an override on the derived class method, which you probably already know.  
If you don't put a modifier on a base class method, polymorphism can't ever happen.  If you then add a non-modified method to the derived class with the same signature as the non-modified base class method, the compiler will generate a Warning message. 
See Following Example:-
namespace PolymorphismBysatyasingh
{
    class Program
    {
        public class Base
        {

            public void Show()
            {
                Console.WriteLine("Show From Base Class.");
            }
        }

        public class Derived : Base
        {
            //Following line will Give an Warning
            /*
             'PolymorphismByManishAgrahari.Program.Derived.Show()'
  hides  inherited member
             'PolymorphismByManishAgrahari.Program.Base.Show()'.
              Use the new keyword if hiding was intended.  
            */
            public void Show()
            {
                Console.WriteLine("Show From Derived Class.");
            }
        }
        static void Main(string[] args)
        {
            Base objBase = new Base();
            objBase.Show();//    Output ----> Show From Base Class.

            Derived objDerived = new Derived();
            objDerived.Show();//Output--> Show From Derived Class.


            Base objBaseRefToDerived = new Derived();
            objBaseRefToDerived.Show();//Output--> Show From Base Class.

            Console.ReadLine();
        }
    }
}


It means that you are hiding (re-defining) the base class method. 
In other languages, take Java for instance, you have what is called "implicit" polymorphism where just putting the method in the derived class with the same signature as a base class method will enable polymorphism. 
In Java, all methods of a class are virtual by default unless the developer decides to use the final keyword thus preventing subclasses from overriding that method. In contrast C# adopts the strategy used by C++ where the developer has to use the virtual keyword for subclasses to override the method. Thus all methods in C# are non virtual by default.


The C# approach is more explicit for the purpose of making the code safer in versioning scenarios.  i.e. You build your code based on a 3rd party library and use meaningful, but common, method names.  The 3rd party library upgrades, using the same common method name.  With implicit polymorphism the code would break, but with C# you would receive a compiler warning so you can double check to see if polymorphism was something you wanted to do.


Difference between Method Overriding and Method hiding
Method overriding allows a subclass to provide a specific implementation of a method that is already provided by base class. The implementation in the subclass overrides (replaces) the implementation in the base class.
The important thing to remember about overriding is that the method that is doing the overriding is related to the method in the base class.
When a virtual method is called on a reference, the actual type of the object to which the reference refers is used to determine which method implementation should be used. When a method of a base class is overridden in a derived class (subclass), the version defined in the derived class is used. This is so even should the calling application be unaware that the object is an instance of the derived class.
namespace PolymorphismBysatyasingh
{
    class Program
    {
        public class Base
        {
     
            public virtual void Show()
            {
                Console.WriteLine("Show From Base Class.");
            }
        }

        public class Derived : Base
        {
//the keyword "override" change the base class method.
            public override void Show()
            {
                Console.WriteLine("Show From Derived Class.");
            }
        }
        static void Main(string[] args)
        {
            Base objBaseRefToDerived  = new Derived();
            objBaseRefToDerived .Show();//Output--> Show From Derived Class.
          
            Console.ReadLine();
        }
    }
}
Output--> Show From Derived Class
Method hiding does not have a relationship between the methods in the base class and derived class. The method in the derived class hides the method in the base class.
namespace PolymorphismBysatyasingh
{
    class Program
    {
        public class Base
        {

            public virtual void Show()
            {
                Console.WriteLine("Show From Base Class.");
            }
        }

        public class Derived : Base
        {

            public new void Show()
            {
                Console.WriteLine("Show From Derived Class.");
            }
        }
        static void Main(string[] args)
        {
            Base objBaseRefToDerived  = new Derived();
            objBaseRefToDerived .Show();//Output--> Show From Base Class.
          
            Console.ReadLine();
        }
    }
}
Output is:à Show From Base Class.
In the preceding example, Derived.Show will be called; because, it overrides Base.Show. 

  • The c# language specification states that  "You cannot override a non-virtual method." see following example:-
namespace PolymorphismByManishAgrahari
{
    class Program
    {
        public class Base
        {

            public void Show()
            {
                Console.WriteLine("This is Base Class.");
            }
        }

        public class Derived : Base
        {
            //Following Line will give error.
            /*
             Error:- 'PolymorphismByManishAgrahari.Program.Derived.Show()'
cannot override inherited member  'PolymorphismByManishAgrahari.Program.Base.Show()'
             * because it is not marked virtual, abstract, or override
             */
            public override void Show()
            {

                Console.WriteLine("This is Derived Class.");
            }
        }
        static void Main(string[] args)
        {
            Base objBase = new Base();
            objBase.Show();//    Output ----> This is Base Class.

            Derived objDerived = new Derived();
            objDerived.Show();//Output--> This is Derived Class.

            Base objBaseRefToDerived = new Derived();
            objBaseRefToDerived.Show();//Output--> This is Base Class.

            Console.ReadLine();
        }
    }
}
Error:- 'PolymorphismBysatyasingh.Program.Derived.Show()' cannot override inherited member 'PolymorphismBysatyasingh.Program.Base.Show()' because it is not marked virtual, abstract, or override

Sealed keyword:-
Sealed keyword can be used to stop method overriding in a derived classes.
By default, all methods a sealed, which means you can't override them, so that "sealed" keyword is redundant in this case and compiler will show you error when you'll try to make sealed already sealed method. But if your method was marked as virtual in a base class, by overriding and marking this method with "sealed" will prevent method overriding in derived classes.
See following example:-
namespace satyasingh
{
    class Program
    {
        public class Base
        {

public sealed void Show()//This Line will give an error - "cannot        
{                      //be sealed because it is not an override"

                Console.WriteLine("This is Base Class.");
            }
        }

        public class Derived : Base
        {
            public void Show()
            {

                Console.WriteLine("This is Derived Class.");
            }
        }
        static void Main(string[] args)
        {
            Base objBaseReference = new Derived();
            objBaseReference.Show();// Output ---------> This is Base Class.

            Console.ReadLine();
        }
    }
}

Error:-
'PolymorphismBySatyasingh.Program.Base.Show()' cannot be sealed because it is not an override

To Remove Error from Above Program use following:-
namespace PolymorphismByManishAgrahari
{
    class Program
    {
        public class Base
        {

            public virtual void Show()    
            {                     
                Console.WriteLine("This is Base Class.");
            }
        }

        public class Derived : Base
        {
            public override sealed void Show()
            {

                Console.WriteLine("This is Derived Class.");
            }
        }

        static void Main(string[] args)
        {
            Base objBaseReference = new Derived();
            objBaseReference.Show();// Output ---> This is Derived Class.

            Console.ReadLine();
        }
    }
}
Output ---> This is Derived Class.

Summary:-
1.        It is not compulsory to mark the derived/child class function with override keyword while base/parent class contains a virtual method
2.       Virtual methods allow subclasses to provide their own implementation of that method using the override keyword
3.       Virtual methods can't be declared as private.
4.       You are not required to declare a method as virtual. But, if you don't, and you derive from the class, and your derived class has a method by the same name and signature, you'll get a warning that you are hiding a parent's method
5.        A virtual property or method has an implementation in the base class, and can be overridden in the derived classes.
6.       We will get a warning if we won't use Virtual/New keyword.
7.        Instead of Virtual we can use New Keyword 

Comments

Post a Comment

Popular posts from this blog

SQL SERVER noteS......ip notes....

                                FUNCTION CREATE FUNCTION Addition() RETURNS Decimal(6,3) After specifying the type of value that the function would return, you can create a body for the function. The body of a function starts with the  BEGIN  and ends with the  END  keywords. Here is an example: CREATE FUNCTION Addition() RETURNS Decimal(6,3) BEGIN END Optionally, you can type the  AS  keyword before the  BEGIN  keyword: CREATE FUNCTION Addition() RETURNS Decimal(6,3) AS BEGIN END Between the  BEGIN  and  END  keywords, which is the section that represents the body of the function, you can define the assignment the function must perform. After performing this assignment, just before the  END  keyword, you must specify the value that the function returns. Thi...
Read more

page life cycle in asp.net.......

Image
Asp.net application and pagelifecycle Introduction In this article, we will try to understand what the different events are which take place right from the time the user sends a request, until the time the request is rendered on the browser. So we will first try to understand the two broader steps of an ASP.NET request and then we will move into different events emitted from ‘ HttpHandler ’, ‘ HttpModule ’ and ASP.NET page object. As we move in this event journey, we will try to understand what kind of logic should go in each and every one of these events. This is a small Ebook for all my .NET friends which covers topics like WCF, WPF, WWF, Ajax, Core .NET, SQL, etc. You can download the same from here or else you can catch me on my daily free training here . The Two Step Process From 30,000 feet level, ASP.NET request processing is a 2 step process as shown below. User sends a request to the IIS: ASP.NET creates an environment which can process the request. In other words, it crea...
Read more

ASP.Net Page Life Cycle

Understanding the Pagelife cycle is important to develop ASP.Net application. The general Page Life Cycle Stages are: 1. Page request - Here Page is requested by the user. 2. Start – Sets the properties such as Request, Response, IsPostBack and UICulture. 3. Page initialization - Controls on the page are available and each control's UniqueID property is set. 4. Load – Controls are loaded here if it is a PostBack request. 5. Validation – Sets the IsValid property. 6. Postback Event handling – Event handlers will be called if it is PostBack. 6. Rendering - the page calls the Render method for each control, providing a text writer that writes its output to the OutputStream of the page's Response property. 7. Unload - Unload is called after the page has been fully rendered, sent to the client, and is ready to be discarded. Common life cycle Events: 1. PreInit – Start event of the Page life cycle and here every page controls are initialized. 2. Init – This is used to read or initia...
Read more