Strategy and Indicator superclass

[koganam]

In the LogHelper class - so that I don't have to write it repeatedly in the indicators and strategies that use it.

All the more reason to use partial classes. All those methods are then natively available.

[adamus]

All the more reason to use partial classes. All those methods are then natively available.

Maybe I don't know enough C# but I thought that wouldn't be possible, since I want to use the LogHelper in indicators and in strategies - are you saying I can code partial class that is a partial class of both Strategy and of Indicator? And aren't namespaces an issue?

And when you say "natively available", do you mean that instead of

logHelper.log("stuff");

I could just do this?:

log("stuff");

[NinjaTrader_JC]

Hello adamus,

While partial classes are something that we cannot support here are a few examples that may help you out.

http://www.dotnetperls.com/partial

http://stackoverflow.com/questions/3601901/why-use-partial-classes

http://msdn.microsoft.com/en-us/library/wa80x488.aspx

[koganam]

Hello adamus,

While partial classes are something that we cannot support here are a few examples that may help you out.

http://www.dotnetperls.com/partial

http://stackoverflow.com/questions/3601901/why-use-partial-classes

http://msdn.microsoft.com/en-us/library/wa80x488.aspx

Huh? Do you support UserDefinedMethods.cs that you ship? They are partial classes.

[koganam]

Maybe I don't know enough C# but I thought that wouldn't be possible, since I want to use the LogHelper in indicators and in strategies - are you saying I can code partial class that is a partial class of both Strategy and of Indicator? And aren't namespaces an issue?

And when you say "natively available", do you mean that instead of

logHelper.log("stuff");

I could just do this?:

log("stuff");

Not quite. That would depend on how you define/override the method. OTOH, you would not have to say Indicator.Print() or Indicator.Log(), nor their Strategy analogs, as they would both be natively supported as simply Print() and Log(). While you can embed a class in another class, that would not even be necessary. You could pretty much just define them as methods of the partial class itself, and call them as necessary.

[adamus]

Not quite. That would depend on how you define/override the method. OTOH, you would not have to say Indicator.Print() or Indicator.Log(), nor their Strategy analogs, as they would both be natively supported as simply Print() and Log(). While you can embed a class in another class, that would not even be necessary. You could pretty much just define them as as methods of the partial class itself, and call them as necessary.

OK thanks. But wouldn't I have to maintain two different versions of my log-helper stuff? One for Indicator namespace and one for the Strategy namespace?