Features of the mql5 language, subtleties and tricks - page 119
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
And you can't go to the bottom one. That's why everything is clear.
Only please with the possibility to declare classes-structures beforehand :)
There is less flexibility.
Flexibility is a disruption to the order in which the algorithm is executed? )
Only please with the possibility to declare classes-structures in advance :)
Well, it doesn't contradict logic. Just like a preliminary declaration of a function. If something is declared earlier, it will be initialized earlier, too. Everything is logically connected.
Is flexibility a violation of the order in which the algorithm is executed? )
Now OnTick can be called from anywhere in the program.
OnTick can now be called from anywhere in the programme.
Well, it doesn't contradict logic. Just like a prior declaration of a function. If something is declared earlier, it will be initialized earlier, too. Everything is logically connected.
It may contradict your logic, but it doesn't contradict common logic for a second. Because everything is guaranteed to be initialized by the moment the code's execution starts.
This may contradict your logic, but it doesn't contradict conventional logic for a second. Because everything is guaranteed to be initialized by the time the code is executed.
You seem to have misread my post. It says it does NOT contradict)
You don't seem to have read my post carefully. It said NOT to contradict).
That's right, I apologise, it happens.
If you need it, you may declare void OnTick(); at the very beginning. But in general the order of declaration of functions is an additional way to control code correctness. For example, if in some plug-in inluder OnTick() or even worse - OnInit() is accidentally called, is it good? Libraries must not see your working code.
What to do when including libraries, each of which includes the same libraries inside itself?
What do I do when I connect libraries that each connect the same library internally?
What to do when connecting libraries, each of which connects the same library inside itself?
it's strange that the directives are entered but not used