{"id":12,"date":"2007-05-12T10:00:07","date_gmt":"2007-05-12T08:00:07","guid":{"rendered":"http:\/\/blog.eweibel.net\/?p=12"},"modified":"2007-05-12T10:00:20","modified_gmt":"2007-05-12T08:00:20","slug":"explicit-interface-implementation","status":"publish","type":"post","link":"https:\/\/blog.eweibel.net\/?p=12","title":{"rendered":"Explicit interface implementation"},"content":{"rendered":"

In C# you have a feature, which java don’t have. It’s called explicit interface implementation.
The main use of this feature is to solve problems when you have to implement for example two interfaces which have both unfortunatly a same method signature:<\/p>\n

namespace testpw.ExplicitInterfaces
{
    public interface IA
    {
        void doAction();
    }<\/p>\n

    public interface IB
    {
        void doAction();
    }
}<\/p>\n

The implementation of both interfaces on the same class look now like this:<\/p>\n

namespace testpw.ExplicitInterfaces
{
    public class TestImpl : IA, IB
    {
        void IA.doAction()
        {
            Console.WriteLine(“Called doAction on interface IA”);
        } <\/p>\n

        void IB.doAction()
        {
            Console.WriteLine(“Called doAction on interface IB”);
        }
    }
} <\/p>\n

One of the benefit of the exlicit interface implementation is, that you could solve this a little bit exotic problem. An other possibility to use explicit interface implementation is, when you have an existing object-structure and you have to extend it with some infrastructure-logic. This new logic you want to hidden to the consumer of the object-structure, so you could use the explicit interface implementation to hide this new logic.<\/p>\n

But, I saw also other interpretations how to use the explicit interface implementation:<\/p>\n