I have a conceptual question about an indicator script which can return multiple public properties.
When I assign those values in a third indicator (or strategy) for example:
double M_I_PV1 = MyIndicator(Close, 14)[0].PublicValue1 ; double M_I_PV2 = MyIndicator(Close, 14)[0].PublicValue2 ;
It doesn't seem to matter from a performance standpoint, I'm just wondering.
If it does matter, then would it be better to have the indicator return an object which encapsulates multiple properties, and then access those properties during assignment to local variables?
object MyIndReturnObj = MyIndicator(Close, 14)[0] ; double M_I_PV1 = MyIndReturnObj.PublicValue1; double M_I_PV2 = MyIndReturnObj.PublicValue2;
If I reference a third line to the same indicator, but using different arguments / parameters, I believe NT must create a separate instance of that object because it is using different input arguments / parameters, is that correct?
Thanks.

Comment