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
Thanks, it's just that the default is kind of weird without it.
Set up the chart as you need it, and save the template under the default name
I can't understand why for writing:
compiler is unhappy: possible loss of data due to type conversion , because it's an integer everywhere. Of course, I could leave it as it is, but the warning is a bit of a nuisance.
I can't understand why for recording:
compiler is unhappy: possible loss of data due to type conversion , because integer is everywhere. Of course, we could leave it as it is, but the warning is a bit of a nuisance.
Make it like this:
And read this: Type conversionMake it so:
And read this: Type conversionI feel, however, that I need to remedy my lack of knowledge, because while my example above strained the compiler, my example below doesn't strain the compiler, and the situation seems to be similar.
Thank you, it helped. Have read the article.
I feel, however, that I need to eliminate my lack of knowledge, because if for my above example the compiler strained, for the below example the compiler doesn't strain, and the situation seems to be similar.
SymbolInfoInteger returns a value of long type, which is 64-bit. And int is 32-bit, so the compiler rightly generates a warning.
In the second case, SymbolInfoDouble returns a value of the double type and this is the same type of your ask variable. So no losses (even theoretically) may occur here and the compiler won't say a word.
I used to see a section here somewhere dedicated to detected MT5 bugs, but forgot where it is or how to find it...