Keywords have nothing to do with OO; they're pure language design. OO contains the concepts of "virtual" and "non-virtual"; how a specific language maps keywords to those concepts (as in Java's default = virtual and "final" = non-virtual) is up to the individual language.
On 7/7/06, Dean Cleaver <[EMAIL PROTECTED]> wrote:
Because in OO programming, there is no keyword for "non-virtual". It's an OO issue, not a .Net issue. Dino -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of David Lanouette Sent: Saturday, 8 July 2006 11:37 To: [email protected] Subject: [ADVANCED-DOTNET] Virtual methods in .NET - was Implementing an Interface - C# vs. VB.NET Anybody know why methods aren't virtual by default in .NET? It seems like a really bad default to have all methods non-virtual. ______________________________ - David Lanouette - [EMAIL PROTECTED] "Excellence, then, is not an act, but a habit" - Aristotle =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
-- Eric Means [EMAIL PROTECTED] http://www.randomtree.org/eric/ =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
