How to Convert double to int in C?

Question

double a;
a = 3669.0;
int b;
b = a;

I am getting 3668 in b, instead of 3669.

How do I fix This problem? And if have 3559.8 like that also I want like 3559 not 3560.

That's interesting. `3669.0` is exactly representable in floating-point... — Mysticial, Oct 05 '11 at 06:12
@Mysticial: Hmm yes, that number should have been stored as 3669 in floating point format. Perhaps, an issue with the compiler. — Shamim Hafiz - MSFT, Oct 05 '11 at 06:14
Should 3668.51 map to 3669 too? (Are you trying to round, or just clip numbers that are really close?) — Cascabel, Oct 05 '11 at 06:14
The code is a lie. The OP has a complicated calculation that he thinks is resulting in `3669.0` but it's really resulting in slightly less. — Gabe, Oct 05 '11 at 06:14
I ran this and got 3669 in b. Here is the result [link]http://www.ideone.com/yWT5G — yo_man, Oct 05 '11 at 06:16
@ratty: Have you tried compiling and running the exact code in your example? I have, and it works correctly. Put something closer to your real code up. — JeremyP, Oct 05 '11 at 09:02
A good answer [can be found here](https://stackoverflow.com/questions/526070). — nwellnhof, Dec 28 '20 at 23:47

score 64 · Answer 1 · answered Oct 05 '11 at 06:16

I suspect you don't actually have that problem - I suspect you've really got:

double a = callSomeFunction();
// Examine a in the debugger or via logging, and decide it's 3669.0

// Now cast
int b = (int) a;
// Now a is 3668

What makes me say that is that although it's true that many decimal values cannot be stored exactly in float or double, that doesn't hold for integers of this kind of magnitude. They can very easily be exactly represented in binary floating point form. (Very large integers can't always be exactly represented, but we're not dealing with a very large integer here.)

I strongly suspect that your double value is actually slightly less than 3669.0, but it's being displayed to you as 3669.0 by whatever diagnostic device you're using. The conversion to an integer value just performs truncation, not rounding - hence the issue.

Assuming your double type is an IEEE-754 64-bit type, the largest value which is less than 3669.0 is exactly

3668.99999999999954525264911353588104248046875

So if you're using any diagnostic approach where that value would be shown as 3669.0, then it's quite possible (probable, I'd say) that this is what's happening.

Try adding something like `printf("a = %.50f\n", a);` to see the actual value of `a`. — Keith Thompson, Oct 05 '11 at 06:20
@KeithThompson: Personally I use a bit of code I've got in C# which handles the binary value directly :) — Jon Skeet, Oct 05 '11 at 06:24
This is the answer. And an excellent answer at that! My question: What happens when @Jon Skeet's score gets too big for SO? Will our appreciation for Jon Skeet eventually kill SO? — Del, Jan 13 '15 at 10:23

Jeegar Patel · Answer 2 · 2021-02-11T06:01:20.073

7

main() {
    double a;
    a=3669.0;
    int b;
    b=a;
    printf("b is %d",b);
  
}

output is :b is 3669

when you write b=a; then its automatically converted in int

see on-line compiler result :

http://ideone.com/60T5b

This is called Implicit Type Conversion Read more here https://www.geeksforgeeks.org/implicit-type-conversion-in-c-with-examples/

edited Feb 11 '21 at 06:01

answered Oct 05 '11 at 06:14

Jeegar Patel

24,980
49
151
213

"_converted in double_" in `int`? – curiousguy Oct 05 '11 at 06:33
oh ya in int...sory its my mistakes – Jeegar Patel Oct 05 '11 at 06:34

score 3 · Answer 3 · answered Oct 05 '11 at 06:12

3

This is the notorious floating point rounding issue. Just add a very small number, to correct the issue.

double a;
a=3669.0;
int b;
b=a+ 1e-9;

answered Oct 05 '11 at 06:12

Shamim Hafiz - MSFT

20,466
38
110
169

7

There should be no problem here at all, as 3669.0 is exactly representable in binary floating point. – Jon Skeet Oct 05 '11 at 06:13
@JonSkeet: Yes I agree. For this particular number, the issue shouldn't occur. I guess something wrong with the compiler maybe or OP hasn't given exact case that's causing the issue. – Shamim Hafiz - MSFT Oct 05 '11 at 06:15
4

The latter is *much* more likely to be the case, IMO. – Jon Skeet Oct 05 '11 at 06:21

score -2 · Answer 4 · answered Oct 05 '11 at 06:45

-2

int b;
double a;
a=3669.0;
b=a;
printf("b=%d",b);

this code gives the output as b=3669 only you check it clearly.

answered Oct 05 '11 at 06:45

Gouse Shaik

340
1
2
14

How to Convert double to int in C?

4 Answers4

Linked