# Double confirming the calculation method

889

a. Double confirm with you that it's not necessary to use '2' below but ok to use '1' below to compare for "int" types. Correct?

 1.  if (a > b)

2. if (a - b > Point / 2.)

b. How many digits does the number precision reach while need to use '2' for comparing?

Moderator
9643

If comparing integers you have no need to worry about floating point precision.
659

"a > b" should always work as you expected.
14781

wqking: "a > b" should always work as you expected.
Wrong for doubles; it's your not understanding floating point and that some numbers can't be represented exactly. (like 1/10.) Double-precision floating-point format - Wikipedia, the free encyclopedia see The == operand. - MQL4 forum
659

WHRoeder:
Wrong for doubles; it's your not understanding floating point and that some numbers can't be represented exactly. (like 1/10.) Double-precision floating-point format - Wikipedia, the free encyclopedia see The == operand. - MQL4 forum

OP was talking about the operator ">", not "==".

14781

Same thing. If because of floating point round off what should be equal could be come greater.

IF you want to open when price exceeds the last bar high, Bid > High[1] could be true when Bid == High[1] because of round off. If that is unacceptable equality is important.

If the possibility of equality is important, you must understand the links posted.

IF point is 0.00001 then 0.999995000000 is the same price as 1.000004999999 but they are not equal.

Moderator
9643

jollydragon:

a. Double confirm with you that it's not necessary to use '2' below but ok to use '1' below to compare for "int" types. Correct?

889

GumRai:

Thank you. But who can help clarify on this question:

b. How many digits does the number precision reach while need to use formula '2' for comparing?

14781