It will be very amazing, cool and very helpful to have multiple interfaces inheritance. I have to write so much redundant code to work around this limitation of MQL language. But on my opinion it's not difficult to implement multiple interfaces inheritance rather than multiple classes inheritance. I'll be very happy if this issue would appear at TODO list for MQL language improvements.
It will be very amazing, cool and very helpful to have multiple interfaces inheritance. I have to write so much redundant code to work around this limitation of MQL language. But on my opinion it's not difficult to implement multiple interfaces inheritance rather than multiple classes inheritance. I'll be very happy if this issue would appear at TODO list for MQL language improvements.
If it's "not difficult", why not coding it yourself ?
You could create a tool, library or whatever, which would allow to use multiple interface inheritance and produce standard MQL code that would compile.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
We have interfaces in MQL but they really don't provide much value than just using an abstract base class in my opinion.
Interfaces become alive when you can inherit a class from multiple interfaces.
I could tag any of my classes with the IIsWaitable and allow them to be used in a wait group
Do we know if they have any plans for this?