Why is the two parameter constructor called when single parameter constructor is expected?

Question

I have the following two constructors in my base class:

protected ExternalSystemException( params Object[] args ) 
    : this( null, null, args ) {}

protected ExternalSystemException( String propertyKeySuffix, 
    params Object[] args ) : this( propertyKeySuffix, null, args ) {}

My child class has the following constructor:

public InvalidPathToOutputFiles(string invalidPath) 
    : base(invalidPath) {}

My client logic instantiates the child class like so:

throw new ChildClass( "goofy" );

When I step through the logic I unexpectedly end up at the base constructor with the parameters ( String propertyKeySuffix, params Object[] args ). I expected the other base class constructor to be called, namely ( params Object[] args ).

Can someone tell me why this is happening?

As soon as I hit submit I wanted to take this one back.

Don
– Don

2010-08-18 21:24:40 +00:00
Commented Aug 18, 2010 at 21:24 — Don
– Don, Commented Aug 18, 2010 at 21:24

Robert Harvey · Accepted Answer · 2010-08-18 21:20:45Z

8

The string overload is the best match to the type you are providing to the constructor. The Params are optional (and Object is ambiguous), so since the second overload has a string type that matches the string type you are passing, the second overload is selected.

answered Aug 18, 2010 at 21:20

Robert Harvey

182k48 gold badges349 silver badges516 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Why is the two parameter constructor called when single parameter constructor is expected?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related