float and integers

[c.lang.myself]

consider following code snippet..
________________________
float a=3.0;
int b=1,c=2;
printf("%d %d %d ",a,b,c);
_________________________

above code give output
0 0 0
i can understand first zero as wrong format(%d) given for a,but i
could not get that why b and c are also printing as zero....

 

[vippstar]

consider following code snippet..
________________________
float a=3.0;
int b=1,c=2;
printf("%d %d %d ",a,b,c);

a is float. %d expects int. You invoked UB, you can't expect anything
from your program.

 

[Keith Thompson]

consider following code snippet..
________________________
float a=3.0;
int b=1,c=2;
printf("%d %d %d ",a,b,c);
_________________________

above code give output
0 0 0
i can understand first zero as wrong format(%d) given for a,but i
could not get that why b and c are also printing as zero....

Once you invoke undefined behavior, all bets are off. By attempting
to print a float object with a "%d" format, you lied to the system;
it's under no obligation to do anything else you ask of it.

Here's one plausible scenario for the behavior you're seeing:

An argument of type float is promoted to double. It's likely that int
is 32 bits and double is 64 bits on your system. So you're passing a
64-bit quantity to printf, and printf is then attempting to grab
argument values of size 32, 32, and 32.

That's only one possibility for what's going on when you run your
program. But really, analyzing just what's happening is most likely a
waste of time. You code has an error; the answer is to fix it.