Why methods in C# are not automatically virtual?
Posted
by Alon
on Stack Overflow
See other posts from Stack Overflow
or by Alon
Published on 2010-04-16T14:20:30Z
Indexed on
2010/04/16
14:23 UTC
Read the original article
Hit count: 241
It would be much more less work to define which methods are NOT overideable instead of which are overideable because (at least for me), when you're designing a class, you don't care if its heirs will override your methods or not...
So, why methods in C# are not automatically virtual? What is the common sense in this?
© Stack Overflow or respective owner