but I'm not sure about that binding to specific values are correct for all cases. I added new unit-tests and this also looks good, so ...
Currently I implemented this via 0x29 opcode (Calli), and the all arguments should be pushed onto the stack before each calling.
Thus the cached TDyn should be valid for custom values via std. stack
for(int i = 0; i < mParams.Length; ++i) {
il.Emit(OpCodes.Ldarg, i);
}
Use IProvider.Cache if not, and report about this here.
For planned v1.3 I implemented new caching of the binding in core provider
test via snet tool (part of regXwild)
x32 library:
x64 library:
looks good !
old result:
but I'm not sure about that binding to specific values are correct for all cases. I added new unit-tests and this also looks good, so ...
Currently I implemented this via 0x29 opcode (Calli), and the all arguments should be pushed onto the stack before each calling. Thus the cached TDyn should be valid for custom values via std. stack
Use IProvider.Cache if not, and report about this here.