getchar-EOF

[Randy]

On page 16 of K&R, 2nd ed., we are given the following program:

[code:18jjlwb2]
#include <stdio.h>

main()
{
     int c;
     c=getchar();
     while (c != EOF) {
          putchar(c);
          c = getchar();
     }
}
[/code:18jjlwb2]

I tried to write a program that did the same without looking at the code and I ended up with nearly the same thing, but I used the "char" type instead of the "int" type as they did. The book explained this in the following way:

"We must declare 'c' to be a type big enough to hold any value that 'getchar' returns. We can't use 'char' since 'c' must be big enough to hold EOF in addition to any possible 'char'. Therefore we use 'int'. "

I still don't understand why 'int' must be used instead of 'char'. If 'int' can hold any value, why can't 'char' as well?

[Anonymous]

I still don't understand why 'int' must be used instead of 'char'. If 'int' can hold any value, why can't 'char' as well?

Because char can only hold/ display alpha char but int can hol/ PERFORM both char and numerals up to 255.
I hope this helps and I pray I am not wrong about this either.  I am really sure about my answer.

[Randy]

OK, thanks, I wasn't aware of that. Makes more sense. :)

[Mr. Cool]

[quote:3llro6cs]Baton Rouge, LA, USA
[/quote]
Are you attending LSU. I used to live in shreveport, go LSU. I miss mardi gra.  Those were party times.
anyway "Hello!"
 

[Randy]

I graduated from LSU back in '96. I am an analyst now, but have never learned C (my major was math) and thought it was well-past time I learned how to code in a "real" UNIX language so am trying now.

[Anonymous]

[quote:11bryrmz]I am an analyst now, but have never learned C (my major was math) [/quote]
Thats' cool, Randy.
Would it be alright if I have any questions about math that I can ask you.
If you have any questions about C or computers. Don't be afraud to ask.
By the way GO TIGERS!

[Randy]

Sure, be my guest, I will answer anything if I can. :)