from a tutorial

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

hey all,

i saw this example and had a question:

Imports System

Namespace MySpace

Public Class Foo : Inherits Bar

Dim x As Integer

Public Sub New()
MyBase.New()
x = 4
End Sub

Public Sub Add(x As Integer)
Me.x = Me.x + x
End Sub

Overrides Public Function GetNum() As Integer
Return x
End Function

End Class

End Namespace

' vbc /out:libraryvb.dll /t:library
' library.vb

Does this mean that if this class gets instantiated there will be 2 objects
because of the MyBase.New line? what would be the reasons for using the line
mybase.new?

thanks,
rodchar
 
Does this mean that if this class gets instantiated there will be 2
objects
because of the MyBase.New line? what would be the reasons for using
the line mybase.new?
Click to expand...

No, one object. Mybase.new initializes the base class.
 
rodchar said:
Does this mean that if this class gets instantiated there will be 2
objects
because of the MyBase.New line? what would be the reasons for using the
line
mybase.new?
Click to expand...

It's one object, but each instance of the derived class is an instance of
the base class too (inheritance /extends/ the base class, it adds something
to it). That's why the base class' constructor has to be called. There are
some situations where it's not necessary to explicitly call it -- in these
cases, the compiler will add the call to the base class' 'New' method.
 
Rodchar,

Almost Lucas text with one little addition

No, one object. Mybase.new initializes the inherited part of the class.

I hope this helps?

Cor
 
It's one object, but each instance of the derived class is an instance of
the base class too (inheritance /extends/ the base class, it adds something
to it). That's why the base class' constructor has to be called. There are
some situations where it's not necessary to explicitly call it -- in these
cases, the compiler will add the call to the base class' 'New' method.
Click to expand...

And in fact this is one of those times. If the call to MyBase.New were
deleted, the compiler would implicitly put it right back in anyway.
 
David said:
And in fact this is one of those times. If the call to MyBase.New were
deleted, the compiler would implicitly put it right back in anyway.
Click to expand...

Yep. That's the case for parameterless constructors.
 
Back
Top