An Inheritance Question.

[Quentin Huo]

Hi:

I have a parent class "classA", which is like:

public abstract class classA
{
.....

public string ReturnAString()
{
return "Hello, World";
}

......
}

And I have another class "classB" inheriting from "classA", like:

public class classB
{
......

public string AMethod()
{
return ReturnAString() ;
}

......
}

My question is: what is the difference if I change the statement
"ReturnAString( );" in the method "AMethod" of the "classB" to:

return base.RetuenAStr ing();

They both works well, but I want to know if there is any difference between
the two statements. The "base" here means an instance of its parent class
has been created? Or maybe they are totally same?

Thanks

Q.

[Bruce Wood]

There is only one subtle difference.

If, two years from now, you were to write another method in classB:

public new string ReturnAString()
{
return "Been around the world!";
}

then simply calling "ReturnAString( );" in classB would result in "Been
around the world", while calling "base.ReturnASt ring()" would result in
"Hello, world".

In other words, unless there is also a method in classB called
ReturnAString, there is no difference at all. Most people don't worry
about the above scenario, and simply code "ReturnAString( )",
understanding that it will invoke the base class method. Besides, if
you were to add a new ReturnAString() to classB, who's to say that you
don't want it called in that situation, and want the base method
instead?

I use "base." only when the derived class already has a method by that
name and I don't want to call it. The classic example is an override
that wants to make use of its base class functionality:

protected override void OnClick(object sender, System.EventArg s args)
{
// Do some special stuff here...

base.OnClick(se nder, args);
}

I have to say "base." here because I don't want to invoke the same
method recursively... I want to add some of my own code and then
continue with the original implementation of OnClick.

[Quentin Huo]

Thank you very much!

Q.

"Bruce Wood" <br*******@cana da.com> wrote in message
news:11******** *************@z 14g2000cwz.goog legroups.com...

There is only one subtle difference.

If, two years from now, you were to write another method in classB:

public new string ReturnAString()
{
return "Been around the world!";
}

then simply calling "ReturnAString( );" in classB would result in "Been
around the world", while calling "base.ReturnASt ring()" would result in
"Hello, world".

In other words, unless there is also a method in classB called
ReturnAString, there is no difference at all. Most people don't worry
about the above scenario, and simply code "ReturnAString( )",
understanding that it will invoke the base class method. Besides, if
you were to add a new ReturnAString() to classB, who's to say that you
don't want it called in that situation, and want the base method
instead?

I use "base." only when the derived class already has a method by that
name and I don't want to call it. The classic example is an override
that wants to make use of its base class functionality:

protected override void OnClick(object sender, System.EventArg s args)
{
// Do some special stuff here...

base.OnClick(se nder, args);
}

I have to say "base." here because I don't want to invoke the same
method recursively... I want to add some of my own code and then
continue with the original implementation of OnClick.