I believe that all methods in BlitzMAX types are virtual or at least Max deals with the virtual business automatically.
This means that you don't need to do anything special with the base class's method in order to replace in in a derived type.
As a rule, the base class should not be aware of or rely on any derived types in any way.
Similarly any functions that accepts an object of the base type as a parameter should not have to know anything about the possible derived types from which the object might actually have been instantated.
This means that you don't need to do anything special with the base class's method in order to replace in in a derived type.
As a rule, the base class should not be aware of or rely on any derived types in any way.
Similarly any functions that accepts an object of the base type as a parameter should not have to know anything about the possible derived types from which the object might actually have been instantated.