I read this on this website page
http://www.vbip.com/books/1861004915...r_4915_06.asp:

Unlike many object-oriented languages, all methods in VB.NET are virtual.

Now in BOL, Under Perforamce Tips and Tricks in .NET Applications, A .Net
Developer Platform White Paper, at the very bottom, it says:

The JIT cannot inline virtual methods, so you lose a potential optimization
if you get rid of non-virtual methods.

So does this mean any method written in VB cannot be inlined, because they
are compiled as virtual? If so, whats the purpose of NotInheritable, or
NotOverridable?

If someone can point me to someplace that will help me on understanding this
discrepency, I would appreciate it. To this point, I've always understood
that VB.Net methods were not virtual if not declared explicitly as
Overridable, and could therefore have the possibility of being inlined.

Raymond Lewallen
Federal Aviation Administration

Raymond Lewallen <(E-Mail Removed)> wrote:
> I read this on this website page
> http://www.vbip.com/books/1861004915...r_4915_06.asp:
>
> Unlike many object-oriented languages, all methods in VB.NET are virtual.

It's wrong - at least by what I consider the meaning of "virtual" to be
(namely that it can be overridden).

It even says earlier on that by default methods can't be overridden.

--
Jon Skeet - <(E-Mail Removed)>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

This is correct, methods must be explicitly marked 'Overridable'

Regards

--

OHM ( Terry Burns )
. . . One-Handed-Man . . .
If U Need My Email ,Ask Me

Time flies when you don't know what you're doing

"Jon Skeet [C# MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Raymond Lewallen <(E-Mail Removed)> wrote:
> > I read this on this website page
> > http://www.vbip.com/books/1861004915...r_4915_06.asp:
> >
> > Unlike many object-oriented languages, all methods in VB.NET are
virtual.
>
> It's wrong - at least by what I consider the meaning of "virtual" to be
> (namely that it can be overridden).
>
> It even says earlier on that by default methods can't be overridden.
>
> --
> Jon Skeet - <(E-Mail Removed)>
> http://www.pobox.com/~skeet
> If replying to the group, please do not mail me too

So am I correct in my assumption that by default, VB methods are NOT
virtual, which is how I've always understood it?

* "Raymond Lewallen" <(E-Mail Removed)> scripsit:
> So does this mean any method written in VB cannot be inlined, because they
> are compiled as virtual? If so, whats the purpose of NotInheritable, or
> NotOverridable?

'NotOverridable' is the default. You don't need to explicitly write it
in every method's head.

> If someone can point me to someplace that will help me on understanding this
> discrepency, I would appreciate it. To this point, I've always understood
> that VB.Net methods were not virtual if not declared explicitly as
> Overridable, and could therefore have the possibility of being inlined.

You are right -- the author of the text you mentioned is wrong.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

Raymond Lewallen <(E-Mail Removed)> wrote:
> So am I correct in my assumption that by default, VB methods are NOT
> virtual, which is how I've always understood it?

Yup.

--
Jon Skeet - <(E-Mail Removed)>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

> * "Raymond Lewallen" <(E-Mail Removed)> scripsit:
> > So does this mean any method written in VB cannot be inlined, because
they
> > are compiled as virtual? If so, whats the purpose of NotInheritable, or
> > NotOverridable?
>
> 'NotOverridable' is the default. You don't need to explicitly write it
> in every method's head.

That is wrong. 'NotOverridable' means sealed in C# which is not the default
and must be written explicitly.
'NotOverridable' means a method cannot be overridden even if it is ifself a
virtual method.

--
cody

[Freeware, Games and Humor]
www.deutronium.de.vu || www.deutronium.tk

> > Unlike many object-oriented languages, all methods in VB.NET are
virtual.
>
> It's wrong - at least by what I consider the meaning of "virtual" to be
> (namely that it can be overridden).

The author also claims that
" If all constructor methods of the base class require parameters then we
must implement at least one constructor in our subclass and we must
explicitly call MyBase.New from within our constructors. "

In my knowledge we must provide for each ctor of the baseclass a ctor of the
derived class which then calls the base class ctor.

--
cody

[Freeware, Games and Humor]
www.deutronium.de.vu || www.deutronium.tk

cody <(E-Mail Removed)> wrote:
> > It's wrong - at least by what I consider the meaning of "virtual" to be
> > (namely that it can be overridden).
>
> The author also claims that
> " If all constructor methods of the base class require parameters then we
> must implement at least one constructor in our subclass and we must
> explicitly call MyBase.New from within our constructors. "

That's true, I believe. Can you give a counter-example? For instance,
can you provide a class with no constructor specified but which derives
from:

public class Foo
{
public Foo (int i)
{
}
}

?

> In my knowledge we must provide for each ctor of the baseclass a ctor of the
> derived class which then calls the base class ctor.

Not at all. Every constructor in the derived class must call a base
class constructor, but there's nothing to say that you *have* to have
as many derived class constructors as there are base class
constructors.

--
Jon Skeet - <(E-Mail Removed)>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

Cody,

My original post concerned VB, which is what Herfried was referring to, and
he was correct in his post. In VB, NotOverridable is the default. I'm not
sure about C#, as I do 90% of my programming in VB.

Raymond Lewallen
Federal Aviation Administration

"cody" <(E-Mail Removed)> wrote in message
news:u2$(E-Mail Removed)...
> > * "Raymond Lewallen" <(E-Mail Removed)> scripsit:
> > > So does this mean any method written in VB cannot be inlined, because
> they
> > > are compiled as virtual? If so, whats the purpose of NotInheritable,
or
> > > NotOverridable?
> >
> > 'NotOverridable' is the default. You don't need to explicitly write it
> > in every method's head.
>
> That is wrong. 'NotOverridable' means sealed in C# which is not the
default
> and must be written explicitly.
> 'NotOverridable' means a method cannot be overridden even if it is ifself
a
> virtual method.
>
> --
> cody
>
> [Freeware, Games and Humor]
> www.deutronium.de.vu || www.deutronium.tk
>
>