Significance of calling the base

[Frank Rizzo]

In some examples with inheriting, I see the overloaded function always
call its base. For instance, in this case where the ListView control is
being extended.

public class ListViewEx : System.Windows.Forms.ListView
{
protected override void OnColumnClick(ColumnClickEventArgs e)
{
...various code to extend the control

base.OnColumnClick (e);
}
}

What is the significance of the base.OnColumnClick(e)? Is it needed or
is it superfluous? In some examples I see it, in others I don't. Is
there a rule for this?

Thanks.

[Floyd Burger]

it depends on whether you want the base class's OnColumnClick code to run or
not. Sometimes you'll want to completely replace what the base class does
(and you won't call the base class's method), and sometimes you want to
augment what it does (and you'd want to call the base method)

--
Floyd Burger

"Frank Rizzo" <no**@none.com> wrote in message
news:OK**************@TK2MSFTNGP12.phx.gbl...

In some examples with inheriting, I see the overloaded function always
call its base. For instance, in this case where the ListView control is
being extended.

public class ListViewEx : System.Windows.Forms.ListView
{
protected override void OnColumnClick(ColumnClickEventArgs e)
{
...various code to extend the control

base.OnColumnClick (e);
}
}

What is the significance of the base.OnColumnClick(e)? Is it needed or
is it superfluous? In some examples I see it, in others I don't. Is
there a rule for this?

Thanks.

[Jon Skeet [C# MVP]]

Frank Rizzo <no**@none.com> wrote:

In some examples with inheriting, I see the overloaded function always
call its base. For instance, in this case where the ListView control is
being extended.

public class ListViewEx : System.Windows.Forms.ListView
{
protected override void OnColumnClick(ColumnClickEventArgs e)
{
...various code to extend the control

base.OnColumnClick (e);
}
}

What is the significance of the base.OnColumnClick(e)? Is it needed or
is it superfluous? In some examples I see it, in others I don't. Is
there a rule for this?

Well, if you don't call the base implementation, then it obviously
won't do what it would normally do - such as fire the ColumnClick event
in this case. Sometimes you do want to call the base method, sometimes
you don't - but there's no general rule that I know of.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Frank Rizzo]

Jon Skeet [C# MVP] wrote:

Frank Rizzo <no**@none.com> wrote:

In some examples with inheriting, I see the overloaded function always
call its base. For instance, in this case where the ListView control is
being extended.

public class ListViewEx : System.Windows.Forms.ListView
{
protected override void OnColumnClick(ColumnClickEventArgs e)
{
...various code to extend the control

base.OnColumnClick (e);
}
}

What is the significance of the base.OnColumnClick(e)? Is it needed or
is it superfluous? In some examples I see it, in others I don't. Is
there a rule for this?

Well, if you don't call the base implementation, then it obviously
won't do what it would normally do - such as fire the ColumnClick event
in this case. Sometimes you do want to call the base method, sometimes
you don't - but there's no general rule that I know of.

Given that I don't have the source for the ListView control, how would I
know whether or not I should call the base for each specific case?

[Jon Skeet [C# MVP]]

Frank Rizzo <no**@none.com> wrote:

Well, if you don't call the base implementation, then it obviously
won't do what it would normally do - such as fire the ColumnClick event
in this case. Sometimes you do want to call the base method, sometimes
you don't - but there's no general rule that I know of.

Given that I don't have the source for the ListView control, how would I
know whether or not I should call the base for each specific case?

Well, do you want it to do what it would normally do or not? For the
OnXXX, it's really "do you want the normal events to fire" to which the
answer is usually yes, I'd expect.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too