4

I would like to replace the getter/setter for properties using RTTI.

I know that you can access the getter setter with TPropInfo.SetProc/GetProc and I know that these fields points to different data depending if the property uses virtual methods, direct field access or static methods.

I'm interesting on replacing propertiy setters/getters that point to virtual methods with custom virtual methods.

TRttiInstanceProperty(RttiProperty).PropInfo^.SetProc := ? // SomeOtherInstance.Setter
TRttiInstanceProperty(RttiProperty).PropInfo^.GetProc := ? // SomeOtherInstance.Getter
monoceres
  • 4,722
  • 4
  • 38
  • 63
  • 3
    The best approach for what you want to achieve would probably be having virtual getter/setter in the first place and then using virtual method interception. – Stefan Glienke Feb 13 '14 at 09:44

1 Answers1

4

You cannot achieve your goal this way because your question is based on a mis-conception. The RTTI information gives you the getter/setter as specified in the compiled code. But when you access a property, the RTTI information is not consulted. Rather the getter/setter is called directly.

To illustrate, consider the following canonical read only property:

property Count: Integer read GetCount;

You can query this property with RTTI to find out the method that implements the getter. However when you write this in code:

Writeln(Obj.Count);

the compiler translates this to:

Writeln(Obj.GetCount);

and compiles that. At the call site the RTTI information is never consulted. So any attempt to modify the RTTI information will have no impact on code that accesses the property.

You need to find a different solution to your problem.

David Heffernan
  • 601,492
  • 42
  • 1,072
  • 1,490
  • That make sense. Too bad. I'm trying to have a base classes own attributed fields defined in subclasses. To do this I need to know when the field changes. I thought intercepting properties would do the job, but apparently not. – monoceres Feb 13 '14 at 10:37