Friday, March 4, 2011

Calling Overriden Constructor and Base Constructor in C#

I have two classes, Foo and Bar, that have constructors like this:

class Foo
{
    Foo()
    {
      // do some stuff
    }

    Foo(int arg)
    {
      // do some other stuff
    }
}

class Bar : Foo
{
    Bar() : base()
    {
      // some third thing
    }
}

Now I want to introduce a constructor for Bar that takes an int, but I want the stuff that happens in Bar() to run as well as the stuff from Foo(int). Something like this:

Bar(int arg) : Bar(), base(arg)
{
  // some fourth thing
}

Is there any way to do this in C#? The best I have so far is putting the work done by Bar() into a function, that also gets called by Bar(int), but this is pretty inelegant.

From stackoverflow
  • Can't you have the Bar constructor that takes an int invoke the parameterless constructor?

    g . : He also wants to invoke the parameterized constructor of the base class.
    Jim Anderson : Okay, I see now.
  • No, this isn't possible. If you use Reflector to examine the IL that's generated for each constructor, you'll see why -- you'd end up calling both of the constructors for the base class. In theory, the compiler could construct hidden methods to accomplish what you want, but there really isn't any advantage over you doing the same thing explicitly.

    Sunny : OK, why this was down-voted?
    Peter Lillevold : Probably downvoted cause you didn't give a solution to the problem, even though there clearly is one.
    DGGenuine : I think the solution below was what I was looking for
  • Can you put the stuff from Bar() in Bar(int) and call Bar(int) with Bar() with a default value? Then Bar(int) can call the base constructor.

    class Bar : Foo
    {
        Bar() : this(0)
        {
        }
    
        Bar(int arg) : base(arg)
        {
        }
    }
    

    That doesn't exactly answer your question, but depending on your scenario might be a workable solution.

  • I would re-chain constructors, so they are called like

    Bar() : this(0) 
    Bar(int) : Foo(int) initializes Bar
    Foo(int) initializes Foo
    Foo() : this(0)
    

    This is suitable, if parameterless constructors are assuming some kind of default value for int parameter of other constructor. If constructors are unrelated, you probably doing something wrong with your type, or maybe we need more information about what are you trying to achieve.

    Trap : For me this is the way to go.
  • This is only thing I can think of...

     public class Foo
    {
        public Foo()
        {
        }
        public Foo(int? arg): this()
        {
        }
    
    }
    public class Bar : Foo
    {
        private int x;
        public Bar(): this(new int?()) // edited to fix type ambiguity
        {
            // stuff that only runs for paramerless ctor
        }
        public Bar(int? arg)
            : base(arg)
        {
            if (arg.HasValue)
            {
                // Do stuff for both parameterless and parameterized ctor
            }
            // Do other stuff for only parameterized ctor
        }
    }
    
    Sunny : You have +1 for the nullable idea, but it has some flow - if you add another ctor with one argument (of class type, not struct), it'll fail, as now this(null) will not know which one to choose.
    Charles Bretana : yes, thanks for that! fixed it...
  • I would recommend changing your constructor chain to go from least specific to most specific.

    class Foo
    {
        Foo()
        {
          // do some stuff
        }
    
        Foo(int arg): this()
        {
          // do some other stuff
        }
    }
    
    class Bar : Foo
    {
        Bar() : Bar(0)
        {
          // some third thing
        }
    
        Bar(int arg): base(arg)
        {
          // something
        }
    }
    

    Any creation of the Bar object will now call all 4 constructors. Constructor chaining should provide default values to more specific constructors, not the other way around. You should really look at what you are trying to accomplish and make sure what you are doing makes sense. Curt is right that there are technical reasons you can't do this, but there are also logical reasons why you shouldn't.

  • can you take the initialization code for Bar() and make it a method and call it from both constructors, and have the new constructor just call base(arg)?

0 comments:

Post a Comment