Resolve specific MT4 warning "possible loss of data due to..." | Forex Factory

Options

Permalinks
Print Thread

Similar Threads

Broker Challenge "NDD/STP" vs. True "ECN" and "Mkt Mkr" broker talk 46 replies

Dealing with "Invalid Price", "Requote", "Server Busy" in MT4 3 replies

Help: Fix the "shift" of indicator to specific server time 5 replies

EA to place order on specific time and specific price 2 replies

Go to specific dates in MT4 & 1M data from 01/2006 4 replies

Resolve specific MT4 warning "possible loss of data due to..."

  • #1
  • First Post: Aug 2, 2018 6:22am Aug 2, 2018 6:22am
Updating some of my EAs and went to "strict" properties. Starting getting this warning "possible loss of data due to type conversion".

I know this warning is discussed here and there but here are the specifics:

declared global variable

extern int Leverage = 200;

if statement in MM routine follows:

*** if (Leverage >= AccountInfoInteger(ACCOUNT_LEVERAGE)) Leverage = AccountInfoInteger(ACCOUNT_LEVERAGE);
else if (Leverage < AccountInfoInteger(ACCOUNT_LEVERAGE)) Leverage = Leverage;

***getting the warning here

Does anyone know why? It's declared an integer and asking to read an integer.

Of course it doesn't produce a warning unless code is declared "strict".
  • #2
  • Aug 2, 2018 6:32am Aug 2, 2018 6:32am
Quoting Pipologist
Updating some of my EAs and went to "strict" properties. Starting getting this warning "possible loss of data due to type conversion". I know this warning is discussed here and there but here are the specifics: declared global variable extern int Leverage = 200; if statement in MM routine follows: *** if (Leverage >= AccountInfoInteger(ACCOUNT_LEVERAGE)) Leverage = AccountInfoInteger(ACCOUNT_LEVERAGE); else if (Leverage < AccountInfoInteger(ACCOUNT_LEVERAGE)) Leverage = Leverage; ***getting the warning here Does anyone know why? It's declared an...
AccountInfoInteger is a long type, you should do (int)AccountInfoInteger.
  • #3
  • Aug 2, 2018 6:36am Aug 2, 2018 6:36am
OK. Found the solution.

Apparently the type of variable was wrong. According to MQL:

https://www.mql5.com/en/docs/constan...unt_trade_mode

Anyway changed the type from int to long and the warning resolved.

Not quite sure what a "long" variable is, it's the first time I've used it. Will have to look into it later, unless someone here can shed some simple light on it.

The question is I'm using an integer is it still ok....will see.

OK. Looks to be alright, just a difference in length of digits.
  • #4
  • Aug 2, 2018 6:43am Aug 2, 2018 6:43am
Quoting Pipologist
OK. Found the solution. Apparently the type of variable was wrong. According to MQL: https://www.mql5.com/en/docs/constan...unt_trade_mode Anyway changed the type from int to long and the warning resolved. Not quite sure what a "long" variable is, it's the first time I've used it. Will have to look into it later, unless someone here can shed some simple light on it. The question is I'm using an integer is it still ok....will see.
Long is 64-bit, int is 32-bit. Use int for this case (leverage cannot go above 2147483647).
  • #5
  • Aug 2, 2018 7:55am Aug 2, 2018 7:55am
Quoting sakisf
{quote} Long is 64-bit, int is 32-bit. Use int for this case (leverage cannot go above 2147483647).
Ha Ha! That's funny.

Actually I just changed the declaration from int to long and bingo.
  • #6
  • Last Post: Aug 2, 2018 5:31pm Aug 2, 2018 5:31pm
Quoting Pipologist
{quote} Ha Ha! That's funny. Actually I just changed the declaration from int to long and bingo.
I bet a lot of programmers are cringing at the thought of this, lol.
0 traders viewing now