Here, too. Apparently, NormalizeDouble requires int, but in fact declared long DIGITS_ = SymbolInfoInteger(a_symbol,SYMBOL_DIGITS); But why int, if generally no more than 10 decimal places in practice? What's the best way to remove the notice in this code?
Second point: price values come from the server normalised, so there is not much point in additionally normalising the value BID_=last_tick.bid (lines 4216-4217).
AAAA!!!!!! You know, looked and looked - I think I got it!!!! The variable is already declared globally, and if I declare it again, its value can become anything. But this is a function, what is declared inside the function is not visible globally, but only inside the function.
Dimka-novitsek: Tell me what he doesn't like. Yes, the variable magik is declared globally like this, so what?
It's a warning that declaring a variable on the specified line hides a variable of the same name declared on line 250. See the scope of variables section in the Reference Manual.
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
Oops, so this long is just the opposite just huge!!!!!
It's just that int DIGITS_ = SymbolInfoInteger(a_symbol,SYMBOL_DIGITS); Also draws a remark!