Is it vooddoo? Why is e-05 added at the end of some of my doubles? A search engine query didn't help.
This is weird. My Expert Advisor was working and 5 minutes later I couldn't make it work again.
Investigating led me to this issue. It seems like some numbers get corrupted, because NormalizeDouble() and other functions taking doubles as input will only output zero with them.
Note that I didn't touch the problematic function before it broke. And the little I changed I converted to comments to narrow down the problem.
Thanks for your input. I just saw other threads about this notation on the forum, but in my case most of the problematic numbers don't have a leading 1.
Still wondering how the code could break suddenly without reason.It hasn't "broke without reason." You just didn't notice it before. 1E-5 is less characters than 0.00001.
question about decima of marketinfo() - MQL4 programming forum
It hasn't "broke without reason." You just didn't notice it before.
I would have noticed if didn't work, but like I said it was working and BOOM, it stopped working out of nowhere 5 minutes later.
1E-5 is less characters than 0.00001.
Thanks for your input. I just saw other threads about this notation on the forum, but in my case most of the problematic numbers don't have a leading 1.
Still wondering how the code could break suddenly without reason.The leading 1 is just an example. E-05 means "move the comma 5 numbers to the left". 234.56 E-05 = 0.0023455 or 234.56 divided by 100000.
Yes but why do other people on the forum get 1e-05? I just noticed that the results I was getting earlier when searching for "e-05" on this forum
have disappeared. Who is messing with me again?
Please guys don't give up.
I found something.
_Point and MarketInfo(_Symbol,MODE_POINT) are both = 1e-05 !?

- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
This is weird. My Expert Advisor was working and 5 minutes later I couldn't make it work again.
Investigating led me to this issue. It seems like some numbers get corrupted, because NormalizeDouble() and other functions taking doubles as input will only output zero with them.
Note that I didn't touch the problematic function before it broke. And the little I changed I converted to comments to narrow down the problem.