Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
As I read here,
the VMT also contains a number of “magic” fields to support features
such as parent class link, instance size, class name, dynamic method
table, published methods table, published fields table, RTTI table,
initialization table for magic fields, the deprecated OLE Automation
dispatch table and implemented interfaces table
It looks like the VMT does not include a field which contains the unit name where the class is defined. Is there some ‘compiler magic’ involved?
I cannot see why the VMT should be involved here. TObject already exposes a
class function UnitNamefor that.System.TObject.UnitName