delphi中的多态性详解（Polymorphism in Delphi）.docVIP

delphi中的多态性详解（Polymorphism in Delphi） Polymorphism in Delphi 2007-04-15 at 12:32, in the talk about polymorphism - concept description, the essence of polymorphism is to assign pointers to subclasses to pointers to the parent class. So why is this assignment permissible or is it safe? Conversely, OK? How is the dynamic binding of virtual functions implemented? These questions will be answered in this article. Suppose you have the following code (described in Object Pascal language): T1 = class Private Member1: integer; Public Function func1: Integer; virtual; Function func2: Integer; virtual; Function func3: Integer; virtual; End; T2 = class (T1) Private Member2: integer; Public Function func1: Integer; override; Function func2: Integer; override; End; The end result is that the memory distribution of the instances of the T1 class is as follows (to illustrate the principle and does not necessarily mean that the compiler must be implemented as well): ______________ _________ | VPTR |------- | T1.func1 | | member1 | | T1.func2 | T1.func3, | | Again Among them, VPTR is a member pointer (called virtual pointer) that is automatically added by the compiler. There is only a virtual function or dynamic function or a pure virtual class will be added to the compiler member pointer, the pointer to a called virtual function table ( Object Pascal became a virtual method table, VMT memory area). The virtual function table holds the entry address for each virtual function. The memory distribution of instances of the T2 class is as follows: _______________ _____________ | VPTR |-------| T2.func1 | | member1 | | T2.func2 | | member2 | | T1.func3 | The most ~~~~~~~~~~~~~ As you can see from the diagram, a subclass object occupies more space than a parent class object. Therefore, when the sub class type pointer assignment assigns the pointer type of the parent class (the so-called upward mapping), also point to the object of class type of memory space is the parent class type pointer