a problem when using int feof(FILE *fp);

[Chad]

In the code that Jens has presented he use fgetc in a loop to read from
a file and output characters until EOF is encountered. The code in the
first pair of #if 0... #endif are simply alternate forms of the same
read loop using instead of fgetc, fscanf and fread. If they had been
compiled (i.e., if the #if 0... #endif were absent), they too would be
executed after the first loop has run it's course. They would most
probably immediately return end-of-file since after the first loop fp
is already read.

This is a case where the #if 0 and #endif are not critical to
correctness, but generally code that has been preprocessed or commented
out should not be compiled without a careful review.

Okay, I think this is the part that is not *clicking*. I don't see
when the code would skip over fgetc() and use something like fread()
instead.

 

[santosh]

Okay, I think this is the part that is not *clicking*. I don't see
when the code would skip over fgetc() and use something like fread()
instead.

It won't "skip over" anything. If you want to use fscanf, you block out
the loops using fgetc and fread. If you want to use fread, you block
out the code using fgetc and fscanf. If you want to use fgetc, you
block out code that uses fscanf and fread, as in the version posted by
Jens. Simple, isn't it?

 

[Chad]

It won't "skip over" anything. If you want to use fscanf, you block out
the loops using fgetc and fread. If you want to use fread, you block
out the code using fgetc and fscanf. If you want to use fgetc, you
block out code that uses fscanf and fread, as in the version posted by
Jens. Simple, isn't it?

Yes.