Method overriding

In addition to providing data-driven algorithm-determined parameters across virtual network interfaces,[1] it also allows for a specific type of polymorphism (subtyping).

[3] This helps in preventing problems associated with differential relay analytics which would otherwise rely on a framework in which method overriding might be obviated.

To favor early error detection (e.g. a misspelling), it is possible to specify when a method is expected to be actually overriding, or not.

[6] In the above example, hiding causes the following: C++ does not have the keyword super that a subclass can use in Java to invoke the superclass version of a method that it wants to override.

Redeclaration also covers effecting, in which an implementation is provided for a feature which was deferred (abstract) in the parent class, and undefinition, in which a feature that was effective (concrete) in the parent becomes deferred again in the heir class.

[8] The intent to redefine a feature, as message in the example below, must be explicitly declared in the inherit clause of the heir class.

Consider a class which uses instances for both THOUGHT and ADVICE: When instantiated, class APPLICATION produces the following output: Within a redefined feature, access to the feature's precursor can be gained by using the language keyword Precursor.

For example: Class Thought represents the superclass and implements a method call message().

Class Advice overrides the method message(), replacing its functionality from Thought.