Errors, bugs, questions - page 1126
![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
I am writing a ToR for an MT4 EA with a priority on accelerated data processing.
Please advise whether the sequence of calculations or sampling (what is the correct name - representative?) is important for speeding up.
I am attaching two variants in the form of pictures showing block diagrams.
If you can, please write how the code should look if the selective execution of the blocks will be - a purely primitive layout, and will this give a significant speed increase!
How is this closing of a position in the tester explained? Is it due to spread widening?
Screenshots from MetaTrader trading platform
EURUSD, M20, 2014.04.12
Alfa-Forex, MetaTrader 5, Real
temp_file_screenshot_63279.png
How is this closing of a position in the tester explained? Is it the widening of the spread?
[img]https://charts.mql5.com/4/434/eurusd-m20-alfa-foreks-temp-file-screenshot-63279-png.png[/img]
If the spread has widened (and judging by the screenshot - by 720 points! on five digits), then everything is correct.
The sell position has closed at the Ask price. This is if the stops were set.
By the way, your brokerAlfa-Forex hasjust gigantic spreads at the end of the week and at the beginning.
Probably they were recorded in the quote history and the tester simulated trading on them.
Stops for the weekend are dangerous - they won't save from the gap anyway, and spread widening can easily catch you.
No error here becauseLONG_MAX+1< 0
Here the warning is valid (t<LONG_MAX always true if t int ) infinite loopThere is no error because ULONG_MAX-1< 0, because the comparison operation is reduced to int
Then how to explain this:
There is no error here because ULONG_MAX-1< 0, i.e. the comparison operation is cast to int or long
Do you mean the comparison in the tested expression in the loop?
Because it doesn't seem that way in a simple comparison.
Just swap them around :)
What does this rearrangement do? t was lower than ULONG_MAX-1 and still is.