Virtual methods are methods that can be overridden by data types derived from the type they were declared in, allowing for polymorphism. In contrast to
Abstract methods, virtual methods must have an implementation, which is used when the virtual is not overridden.
A derived type can override virtual methods declared in its base type by declaring a method with the same identifier and signature, meaning same number and type of parameters, same return type (if any) and same calling convention (if that differs only in parameter passing mode or calling convention or return type, then an overriding error is returned at compile time, else only shadowing is enabled). The property of being a virtual method is not implicitly inherited by the overriding method in the derived type.
When calling virtual methods, the compiler may need to do a vtable lookup in order to find out which method must be called for a given object. This requires an extra hidden vtable pointer field to be added at the top of each type with virtual methods. This hidden vptr is provided by the built-in
Object type. Because of that, virtual methods can only be declared in a type that directly or indirectly
Extends Object.
Constructors cannot be virtual because they create objects, while virtual methods require an already-existing object with a specific type. The type of the constructor to call is determined at compile-time from the code.
In addition, when calling a virtual method inside a constructor, only the local version of the method is used. That is because the vptr has not yet been set up by the derived type constructor, but only by the local type constructor.
Destructors often must be virtual when deleting an object manipulated through a pointer to its base type, so that the destruction starts at the most derived type and works its way down to the base type. To do this, it may be necessary to add virtual destructors with an empty body anywhere an explicit destruction was not yet required.
On the other hand, when calling a virtual (or abstract) method inside a destructor (virtual or not), the derived method is actually used because the vptr and its vtable are yet there. But this is not reliable because child destructors may have already been called, and so the derived method called may refer to destroyed members.
For member methods with
Virtual in their declaration,
Virtual can also be specified on the corresponding method bodies, for improved code readability.
Note: In a multi-level inheritance, a same named method (same identifier and signature) can be declared
Abstract,
Virtual or normal (without specifier) at each inheritance hierarchy level. When there is mixing of specifiers, the usual order is abstract -> virtual -> normal, from top to bottom of the inheritance hierarchy.
The access control (
Public/
Protected/
Private) of an overriding method is not taken into account by the internal polymorphism process, but only for the initial call at compile-time.
A derived static method cannot override a base virtual/abstract method, but can shadow any base method (including virtual/abstract).