Object-Oriented Programming OOP

[Tradewinds 12]

Type defines the properties\functions\events\etc of an object - like a blueprint.

But an object is an instance of the Type - like a house.

 

Maybe another analogy will help here ...

 

tsdata.trading.Order == 'Human'

MyOrder == 'Mark'

 

So MyOrder is an instance of Type tsdata.trading.Order

just as 'Mark' is an instance of Type 'Human'

 

So therefore you can call 'MyOrder.Cancel'

just like you can call 'Mark.Walk'

 

But 'Human.Walk' doesn't make sense because 'Human' is just a definition. 'Mark' is the instance of that definition. Thats why you can call 'tsdata.trading.Order.Cancel'

 

MMS

 

Good explanation. The part about "Human.Walk" makes sense to me. The category 'Human' is to broad, and not specific to one 'instance'. The only way that "Human.Walk" would work, is if it forced all humans on the entire planet to walk. But that wouldn't be very beneficial. It would be like giving the order, All_TL_Members.Post That would be a nightmare. LOL It's better to use: MMS.Post Then we can make some progress. :rofl:

 

tsdata.trading.Order.Cancel would need to cancel every single order. There could be OrderOne, OrderTwo, OrderFutures, OrderStocks, etc. There might be times when you might want to cancel all orders, but you would want a specific command for that. It's important to be able to control one specific instance of something, so there needs to be a way to label and refer to that specific instance.

[MadMarketScientist 11]

It's important to be able to control one specific instance of something, so there needs to be a way to label and refer to that specific instance.

 

Yup that is essentially Object Oriented Programming ... the Objects are the individual instances of a Class. You never really 'control' all the instances of a Class (Human) just the individual instances of the class (Mark)

 

regards,

MMS