Skip to main content

C# Polymorphism - handle with care


Download

Overriding is the base for most of the design patterns which exists. It provides us with an essential tool called Polymorphism .

What is Polymorphism ?
Polymorphism means one interface and many forms. It is a characteristics of being able to assign a different meaning or usage to something in different contexts specifically to allow an entity such as a variable, a function or an object to have more than one form. 

There are two types of Polymorphism. 
Compile time: function or operator overloading 
Runtime: Inheritence & virtual functions

Here, we are going to talk about the Runtime Polymorphism. 


If you read the definition carefully you will see that there is going to be some type casting and compiler is going to made some assumptions. These assumptions may fail on execution. Let me explain this further.



Type casting:
There will be a parent interface (Interface, abstract class, class) and may be many child classes. These child classes will implement the polymorphic behavior in different ways. The consumer will use Parent class' variable and the reference can be changed at runtime. 

Assumptions:
If we are using an interface and we cast an variable to that interface, compiler will assume that some child class of this variable's type will implement the methods specified by the interface. If this will not come out to be true it will throw exception at runtime.



using System;

namespace AbstractClasses
{
    class Program
    {
        static void Main(string[] args)
        {
            Apple fruit = new Apple();
            fruit.Print();
            IContract contract = (IContract) fruit;
            Console.ReadLine();
        }
    }

    internal interface IContract
    {
        void Display();
    }
    #region
    internal abstract class Fruit
    {
        public abstract string Name { get; set; }

        public virtual void Print()
        {
            Console.WriteLine("from abstract class");
        }
    }

    internal class Apple: Fruit
    {
        public override string Name { get; set; }

        public void Print()
        {
            Console.WriteLine("from child");
        }
    }
    #endregion
}

Handle With Care:
There are ways using which we can improve our code. Let us talk about them.

1. We can use 'as' keyword while casting a variable to an interface. This is because using the as operator is a better coding strategy than a straight cast because it yields a null on a conversion failure rather than raising an exception. 

using System;

namespace AbstractClasses
{
    class Program
    {
        static void Main(string[] args)
        {
            Apple fruit = new Apple();
            fruit.Print();
            //IContract contract = (IContract) fruit; //Invalid cast exception

            IContract contract =  fruit as IContract;
            if(contract != null)
                contract.Display();
            Console.ReadLine();
        }
    }

    internal interface IContract
    {
        void Display();
    }
    #region
    internal abstract class Fruit
    {
        public abstract string Name { get; set; }

        public virtual void Print()
        {
            Console.WriteLine("from abstract class");
        }
    }

    internal class Apple: Fruit
    {
        public override string Name { get; set; }

        public void Print()
        {
            Console.WriteLine("from child");
        }
    }
    #endregion
}


2. We can use sealed keyword on classes which we do not want to be inherited. Then the compiler will not assume that the object being cast is going to exhibit polymorphic behavior and will check its cast to the interface at compile time.


using System;

namespace AbstractClasses
{
    class Program
    {
        static void Main(string[] args)
        {
            Apple fruit = new Apple();
            fruit.Print();
            
            IContract contract =  fruit as IContract;
            if(contract != null)
                contract.Display();
            Console.ReadLine();
        }
    }

    internal interface IContract
    {
        void Display();
    }
    #region
    internal abstract class Fruit
    {
        public abstract string Name { get; set; }

        public virtual void Print()
        {
            Console.WriteLine("from abstract class");
        }
    }

    internal sealed class Apple: Fruit
    {
        public override string Name { get; set; }

        public void Print()
        {
            Console.WriteLine("from child");
        }
    }
    #endregion
}


Compile Time Error:
Cannot convert type 'AbstractClasses.Apple' to 'AbstractClasses.IContract' via a reference conversion, boxing conversion, unboxing conversion, wrapping conversion, or null type conversion.

Comments

Popular posts from this blog

Laravel XAMPP MySQL artisan migrate install error mysql.sock

In my previous post I wrote about setting up Laravel 4 on Mac with XAMPP . When I tried to use migrations (using artisan) I faced some issue. I will also post about Laravel migrations soon.    php artisan migrate:install Error :                                                     [PDOException]                                       SQLSTATE[HY000] [2002] No such file or directory                                              Solution : We need to tell artisan which mysql we want it to use. For this to work we need to porivde it with mysql.sock which we want it to use. So change your database settings like this: 'mysql' => array( 'driver'    => 'mysql', 'host'      => 'localhost',     'unix_socket' => '/Applications/xampp/xamppfiles/var/mysql/mysql.sock', 'database'  => 'wedding', 'username'  => 'root', 'password'  => '', '

Add (Drop) a new article (table) at publisher in merge replication

Let us add the article using the GUI first. First of all create the table on publisher database. Now right click on the publisher and select properties from the menu. Click on articles. Uncheck the - "Show only checked articles in the list" checkbox, in order to see the newly added table. Select the table as shown in the figure below. Press ok The article has now been added to the publisher We now need to recreate the snapshot Right click the publication and select – “View snapshot agent status”. Click start to regenerate snapshot. Now right click on the subscription (I have both on same server you may have on different servers) and select “View synchronization status” Click on start on the agent. The schema changes will propagate to the client if you have "Replicate schema changes" property set to true in the publisher.

Check SQL Server Job status (State) using sp_help_job and xp_sqlagent_enum_jobs

This article is about checking the status of a SQL job. In our work place we have lot of SQL jobs. These jobs will run whole day and are business critical. They will load the data and generate extracts which will be used by business people. Thus, it becomes quite essential to support the system efficiently so that the job finishes in time and as desired. Also, while designing a new system sometimes we need to check the dependency of one job over another. In such scenario we need to check whether a particular job has finished or not. All this can be achieved in SQL Server by using the procedures:- sp_help_job xp_sqlagent_enum_jobs Note: xp_sqlagent_enum_jobs is an undocumented proc inside of sp_help_job and is used extensively to get SQL agent job information. sp_help_job: This procedure gives some insight into the status, and information, about a job. This stored procedure provides information such as last start time, job status etc. Syntax sp_help_job { [ @job_id= ] jo