float values can b rounded off?

[sushant]

hi;

the code:

int main(void)
{
float i=6.10203;
printf("%d",i);
return 0;
}
is giving the o/p zero. why??????

[Richard Bos]

"sushant" <th********@rediffmail.com> wrote:

int main(void)
{
float i=6.10203;
printf("%d",i);
return 0;
}
is giving the o/p zero. why??????

Because you're lying to the compiler. Why should it magically figure out
which of the several possible interpretations of this undefined
behaviour you want?

Richard

[Jonathan Burd]

sushant wrote:

hi;

the code:

int main(void)
{
float i=6.10203;
printf("%d",i);
return 0;
}
is giving the o/p zero. why??????

1. No proper indentation (stop using Google to post;
get a real NG client).
2. "I MUST NOT FORGET TO INCLUDE STDIO.H" - Homer (well, not really).
3. Ever heard of coercion?

Regards,
Jonathan.

--
"I'm learning to program because then I can write
programs to do my homework faster." - Andy Anfilofieff

[john_bode]

sushant wrote:

hi;

the code:

int main(void)
{
float i=6.10203;
printf("%d",i);
You're using the wrong conversion specifier in printf(). "%d" expects
an int argument. Use "%f" instead.
return 0;
}
is giving the o/p zero. why??????

Using the wrong conversion specifier leads to unpredictable results.

[Martin Ambuhl]

sushant wrote:

hi;

the code:

int main(void)
{
float i=6.10203;
printf("%d",i);
return 0;
}
is giving the o/p zero. why??????

/* mha: After fixing
* 1) the failure to include <stdio.h>
* 2) the incorrect specifier for a floating-point argument, and
* 3) the failure to end the last line of output with an end-of-line
* character
* we get the working program below
*/
#include <stdio.h>

int main(void)
{
float i = 6.10203;
printf("%g\n", i);
return 0;
}

[CBFalconer]

sushant wrote:

the code:

int main(void)
{
float i=6.10203;
printf("%d",i);
return 0;
}
is giving the o/p zero. why??????

Screw ups:
1. Posting via google and losing all indentation. See sig.
2. Failure to #include <stdio.h>
3. Lying to the compiler about the type of i in the printf.
4. lack of blanks within the code (foolish style).

Either of 2 or 3 result in undefined behavior.

--
"If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers." - Keith Thompson

[Mike Wahler]

"sushant" <th********@rediffmail.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...

hi;

the code:

int main(void)
{
float i=6.10203;
printf("%d",i);
return 0;
}
is giving the o/p zero. why??????

The result could be anything or nothing. The behavior
is undefined.

#include <stdio.h>

int main(void)
{
float i = 6.10203;
printf("%f\n", i);
return 0;
}

Tip: Prefer type 'double' over 'float'. It has
a much greater precision and range of values.

-Mike

[Keith Thompson]

CBFalconer <cb********@yahoo.com> writes:

sushant wrote:

the code:

int main(void)
{
float i=6.10203;
printf("%d",i);
return 0;
}
is giving the o/p zero. why??????

Screw ups:
1. Posting via google and losing all indentation. See sig.
2. Failure to #include <stdio.h>
3. Lying to the compiler about the type of i in the printf.
4. lack of blanks within the code (foolish style).

Either of 2 or 3 result in undefined behavior.

As well as excessive abbreviation. In the subject, it's "be" not "b".
In the body of the article, "output" is much clearer than "o/p".

I understand there's a common writing style that uses very short
abbreviations like "4" for "for", "2" for "to", and so forth. Please
don't use that style here in comp.lang.c.

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.

[Mabden]

"Keith Thompson" <ks***@mib.org> wrote in message
news:ln************@nuthaus.mib.org...

As well as excessive abbreviation. In the subject, it's "be" not "b".
In the body of the article, "output" is much clearer than "o/p".

I understand there's a common writing style that uses very short
abbreviations like "4" for "for", "2" for "to", and so forth. Please
don't use that style here in comp.lang.c.

KT keepin' it real 4 the OG's! You my nigga, dawg!

(Uuuuhhh... that's a good thing, AFAICT)

--
Mabden

[Richard Bos]

Jonathan Burd <jo***********@REMOVEMEgmail.com> wrote:

sushant wrote:

float i=6.10203;
printf("%d",i);
1. No proper indentation (stop using Google to post;
get a real NG client).
2. "I MUST NOT FORGET TO INCLUDE STDIO.H" - Homer (well, not really).

Ahem. That's stdio.h, please. C is case-sensitive.
3. Ever heard of coercion?

Yes, but what has it to do with this code?

Richard

[Mike Wahler]

"Richard Bos" <rl*@hoekstra-uitgeverij.nl> wrote in message
news:41***************@news.individual.net...

Jonathan Burd <jo***********@REMOVEMEgmail.com> wrote:

sushant wrote:

float i=6.10203;
printf("%d",i);
1. No proper indentation (stop using Google to post;
get a real NG client).
2. "I MUST NOT FORGET TO INCLUDE STDIO.H" - Homer (well, not really).

Ahem. That's stdio.h, please. C is case-sensitive.

Ahem, ahem. That's <stdio.h> please.
C is spelling sensitive. :-)

3. Ever heard of coercion?

Is that when a boy and a girl have ercion together?
Yes, but what has it to do with this code?

I think he conceived it while having ercion.

-Mike

[Richard Bos]

"Mike Wahler" <mk******@mkwahler.net> wrote:

"Richard Bos" <rl*@hoekstra-uitgeverij.nl> wrote in message
news:41***************@news.individual.net...

Jonathan Burd <jo***********@REMOVEMEgmail.com> wrote:

sushant wrote:
> float i=6.10203;
> printf("%d",i);

1. No proper indentation (stop using Google to post;
get a real NG client).
2. "I MUST NOT FORGET TO INCLUDE STDIO.H" - Homer (well, not really).

Ahem. That's stdio.h, please. C is case-sensitive.

Ahem, ahem. That's <stdio.h> please.
C is spelling sensitive. :-)

Well... it's either "I must not forget to #include <stdio.h>", or "I
must not forget to include stdio.h", IYAM.

3. Ever heard of coercion?

Is that when a boy and a girl have ercion together?

Si puer cum puellula coercetur in cellula, felix double complex
conj(double complex z)?

Richard

[Michael Mair]

Richard Bos wrote:

"Mike Wahler" <mk******@mkwahler.net> wrote:

"Richard Bos" <rl*@hoekstra-uitgeverij.nl> wrote in message
news:41***************@news.individual.net...

Jonathan Burd <jo***********@REMOVEMEgmail.com> wrote:
sushant wrote:

>float i=6.10203;
>printf("%d",i);

1. No proper indentation (stop using Google to post;
get a real NG client).
2. "I MUST NOT FORGET TO INCLUDE STDIO.H" - Homer (well, not really).

Ahem. That's stdio.h, please. C is case-sensitive.

Ahem, ahem. That's <stdio.h> please.
C is spelling sensitive. :-)

Well... it's either "I must not forget to #include <stdio.h>", or "I
must not forget to include stdio.h", IYAM.

3. Ever heard of coercion?

Is that when a boy and a girl have ercion together?

Si puer cum puellula coercetur in cellula, felix double complex
conj(double complex z)?

Vagantes Burani delectantur; excruciantur ad "restrict"ionem :-)

-Michael
--
E-Mail: Mine is a gmx dot de address.

[Jonathan Burd]

Mike Wahler wrote:

"Richard Bos" <rl*@hoekstra-uitgeverij.nl> wrote in message
news:41***************@news.individual.net...

Jonathan Burd <jo***********@REMOVEMEgmail.com> wrote:

sushant wrote:

float i=6.10203;
printf("%d",i);

1. No proper indentation (stop using Google to post;
get a real NG client).
2. "I MUST NOT FORGET TO INCLUDE STDIO.H" - Homer (well, not really).
Ahem. That's stdio.h, please. C is case-sensitive.

Ahem, ahem. That's <stdio.h> please.
C is spelling sensitive. :-)

Ask HOMER. ;)

3. Ever heard of coercion?

Is that when a boy and a girl have ercion together?

Yes, but what has it to do with this code?

I think he conceived it while having ercion.

-Mike

"Oh yeah, baby!" ;)
</:P>

Regards,
Jonathan.

--
"Women should come with documentation." - Dave