![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
always killed the logic of such a construction in cyclic operands :
completely incomprehensible ...
If you don't understand it, I can only sympathize.
If you ask me, the standard logic is clearer and more understandable:
I find it much more logical to put brackets either on one line or in one column. It is very difficult to understand code in which it is not clear where a block starts or ends. Well, if the purpose of such formatting is to hide the sense of the code from enemies, then the goal is achieved.
I've always been killed by nested if's -- why make such nesting at the source?
If it's not clear, I can only sympathise.
Your logic is not standard. It's wrong.Correction, it's just a phrase that sticks out :-)
--
Unconventional logic doesn't mean it's wrong.
--
when the path of non-standard logic is shorter than that of standard logic -- with equal input and output conditions --
then to hell with standards!
Then I'm all for non-standard logic.
--
yes the crunch code is hard to read...
...although I have seen very short and hard to read code ...
for maintenance - replication this code is not ideal .
If you write it for circulation, you usually have to take care of your colleagues to maintain it .
if you write code with the expectation that someone will break it!
Ideally, it is LOGIC to go through the trouble - you write correctly but make code that is not readable.
I don't understand where the puncture is? And why the second one? If it's the second, then where's the first?
The code that was scolded really isn't super, it's perfect to confuse!
2 Vinin . Victor, why call the order selection function all the time? It's easier to fill in all the variables in one loop.
I think it's pretty good:
int time;
In MQL the behaviour of && and || operators is different than in C++, so it makes sense to separate conditions.
2 Vinin - Victor, why call the order selection function all the time? It's easier to fill all variables in one loop.
...It depends.
I only see the point in increasing the speed of the code
By and large, speed is not crucial in 90% of cases. The point is to initially make the code so that it is as easy to build and read as possible.
Then, if time is crucial, we optimize the speed.
Transferring here from here