![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
true is sometimes false
false sometimes true )
true is sometimes false
LOL! In wartime the sine value can be as high as 4.
There must have been a template and instead of true there was an external variable that included log output. But as there was no such variable in the task, it was deleted. And since programmers are practical people, it was not deleted at all, it was left easy to return it.
If there was an external variable, it would have been easier to set it true/false, but here it is replaced in every if,
I don't see the practicality in this case,
more likely to be a matter of pussyfooting and irresponsibility.
if there was an external variable, it would be easier to set it true/false, but here it's replaced in every if,
I don't see the practicality of it,
it's more likely to be a matter of indifference and irresponsibility.
Yes, it seems to me, too, that there must have been some kind of condition at first, and then, not to take too long to figure it out, they put true and left it there, without thinking about the fact that later they themselves wouldn't understand why it was there.
if(true) is written when debugging, at least that's what I do to get into the block and check if it works
SZZ: it's highly probable that the code has undergone several modifications, and then you can not see such miracles, the customer can not explain that each modification breaks the code structure
I don't understand, can you elaborate?
Can I see the source code from which the code snippet was taken?
Can I see the source code from which this code fragment was taken?
The code is not mine, nor is it public, so I can't show you all of it
if(true) is written when debugging, at least that's what I do to get into the block and check if it works
SZZ: it's highly probable that the code has undergone several modifications, and then you can not see such miracles, the customer can not explain that each modification breaks the code structure
Nonsense
Strange design, what does it mean?
Maybe there is a hidden meaning that I don't know?
I did so when I am asked to give a demo version of my time-limited product. And in that part where it is checking for expiration time of the demo version I mix up the code as much as possible with different additional branching operations in the code like if (1==1) and the like. In case someone decides to decompile the code to complicate understanding of how it all works. :) Although they say that the latest versions of mql are difficult to decompile, but I still do such senseless operations in code just in case.