![MQL5 - Language of trade strategies built-in the MetaTrader 5 client terminal](https://c.mql5.com/i/registerlandings/logo-2.png)
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
As far as I remember, C# is not good friends with mql
https://www.mql5.com/ru/forum/285631
10. MQL5: Added native support for .NET libraries with "smart" function import. Now you can use .NET libraries without writing special wrappers - MetaEditor takes care of that.
It doesn't increase the profitability of strategies.
Referring to the profitability of strategies when discussing programming techniques is rather depressing.
If someone can explain why it helps so much in coding - I'll be glad to learn something new.
You can't even make your own multidimensional array properly. Let alone an array with different types of values. You can't even do it with just one, because such code would not fit into mql:
Of course, you can write d=array[5].to_double(), pretend it should be so and be happy about your ugly code. But if overloading of type conversion operations were allowed, hardly anyone would prefer this way of writing d=array[5].
...
of course you can write d=array[5].to_double(), pretend that this is how it should be and be happy about your buggy code. But if overloading of type conversion operations were allowed, hardly anyone would prefer this way of writing d=array[5].
Straightforward. d=array[5] could:
If we get nerdy, there are still difficulties with array[3] = 4.00123; But it's readable and fine as it is.
Right. d=array[5] is fine:
If you get boring, then there are difficulties with array[3] = 4.00123; But it's readable and good enough as it is.
Yep, d=array[5] is ok. but then you can't make array[5]=d. But you can make %= instead of =. no problem, at the same time the icon will remind us what place everything is done through))
Yeah, d=array[5] can. but then you can't make array[5]=d. But you can make %= instead of =. No problem, and the icon will remind you which place to use))
If you really want to do it, you can do it like this
etc.
I was critical at first too, but then I thought I could use it myself:
I asked for a parenthesis operator and a grapeshot operator about three or four years ago.
you ask, maybe you can do better.
...
of course you can write d=array[5].to_double(), pretend that this is how it should be and be happy about your buggy code. But if overloading of type conversion operations were allowed, hardly anyone would prefer this way of writing d=array[5].
What problems people have))) Oh, bless my life!
By the way, writingd=array[5].to_double() is much easier thand=(double)array[5] Just press a point. But we're not looking for easy ways...