![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
My sincere condolences to the developers, having toexplain the same thing1000 times to every new user...
This is already a blatant attack...
It's written in textbooks about storing real numbers in memory and it doesn't say anything about variables changing by themselves. Although I've heard it not only from SK on this forum.
So if you have misled every new user 1000 times, you should now find them and apologize for your words!
I agree with Simca. When performing arithmetic operations errors are possible, but when storing, writing or reading they are excluded!
That's why I asked the NormalizeDouble() function algorithm, maybe it also has arithmetic operations that cause an error?
What do you think Simca?
OK. You say that so confidently that I'm beginning to doubt what I'm saying.
I used to work on an old PC with 256MB RAM until some time ago. When you google a few programs, the OS would dump some of the data to disk, and then load it up again. Since I modified the code (specifying normalization in comparison operator) the error stopped appearing. But I began to doubt after hearing your words - what if I actually hadn't noticed the error?
Now I don't know whether to apologize or not. If I am wrong, then let 1000 users forgive me.
(but still it's better to perform normalization directly when calculating the comparison operation:)
It's written in textbooks about storing real numbers in memory and it doesn't say anything about variables changing on their own. It's not justSK that I've heard this on this forum though.
But, all this concerns calculations while values stored in memory will not change regardless of whether they are normalized or not.
That's why I was asking the NormalizeDouble() function algorithm, maybe it also has arithmetic operations that cause an error?
What do you think Simca?
(but still it is better to perform normalisation directly when calculating the comparison operation:)
And for my part (for those who do not fully understand the essence of the question) I can also recommend:
(but still, it is better to perform normalisation directly when calculating the comparison operation (c) SK.
(but it is still better to do the normalisation directly when calculating the
the comparison operation is calculated:)
Sorry, but in terms of efficiency there are much better implementations for comparing data requiring normalisation. Basically, this is the standard (comparison algorithm). You have to compare the difference with half the scale dimension. What I mean: to compare prices (whether they are different or not) you should take the difference and compare it to 0.5*Roynt (it can be calculated only once during initialization of the EA/script/indicator. This is much more efficient than calling one function, and even more so if it's also in a loop) .... And it won't matter how this data is stored and to what insignificant sign it is rounded.
Good luck.
Firstly, working with dubles is purely a compiler thing, so to demand convenience from mql4, which is essentially a hidden intrinsic compiler, is unreasonable. The main thing, the developers have given a way to GUARANTEED the correct result of comparison, we checked it with our hands, it is, of course, graphical, but WORKING!!! Although the documentation says that normalize only in case of "!=" or "==", our independent and expert tests have shown that (a>b) DOES NOT WARRANT (!) correct result if a turns out to be equal to b! Even if you PREDVORITELY normalize both a and b, the result is unpredictable. And here is a construction from developers:: NormalizeDouble(a-b, Digits)>0 works reliably! I don't know why folks here don't like normalize function... Maybe it (internally) is quite sempotical done like this: two dables are divided by double precision, and rounded down (or up). And afterwards the integers are compared without any problems.
Please write in proper Russian.
Give me a link to your site and I promise I'll ONLY use the AUTHOR'S DEFINITIONS. :) Your idea, I think, is not more correct than mine, but if YOU PERSONALLY want to understand, I'll do a "spokesman for Rosh", if you can not distinguish between blah-blah and expert appraisal. Because I was not writing to you, but to the 1001st newcomer. :)
For example www.gramota.ru
We do not have an albanian section of the forum. Nevertheless, after the next non-Russian post you will be sent there. Please, don't make it sound like you're using the language.