Any rookie question, so as not to clutter up the forum. Professionals, don't pass by. Nowhere without you - 6. - page 567
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
AlexeyVik, Vladon,
Seems like a normal code. Should we ignore these warnings?What's normal there?
You have a type mismatch (highlighted in red): You are trying to pass a value of type double into type int, which has a much wider value range than int. There may be a loss of value. Surely the compiler warns you about this.
What's the warning?
What's normal about it?
How do I calculate the number of characters?
And how do I know if it is a day off (Saturday, Sunday)?
What about implicit type conversion? Although I agree, it may cause an error. Better to convert directly via StrToInteger.
If you were passing the int in double, there would be no problem. You would be passing a value of a type with a smaller range to a type with a larger range. And there would be no possible loss of data. And, consequently, there would be no warning either.
Hi all!
The MQL4 documentation has changed. The tutorial has not changed.
To use the new features of MQL4 it is necessary to study the MQL5 tutorial ?
Or is there another special literature?
Hi all!
The MQL4 documentation has changed. The tutorial has not changed.
To use the new features of MQL4 it is necessary to study the MQL5 tutorial ?
Or is there another special literature?
No, you don't. If you study 4, study documentation for 4. Although, if anything, the two are somehow intertwined.
As I see it, the compiler is now unified (you can write for both 4 and sub-4). That's why the documentation is the same, except for some differences. Generally, I advise to read documentation for 4 and stay away from 5. It is more complicated, at first sight. You won't lose anything from it.
No, you don't. If you study 4, study the documentation for 4. If anything, though, the two are somehow intertwined.
As I see it, the compiler is now unified (you can write for both 4 and sub). That's why the documentation is the same, except for some differences. Generally, I advise to read documentation for 4 and stay away from 5. It is more complicated, at first sight. You won't lose anything from it.
The description of the functions in the documentation looks cumbersome, unfamiliar, complicated.
A beginner in many ways may not find parallels between the old textbook and the new documentation.
Maybe they will make reference to the old documentation or . new textbook.
I will definitely reread it.