Possible Duplicate:
Why is iostream::eof inside a loop condition considered wrong?
So I've been using the eof()
function in a lot of my programs that require file input, and my professor said that it is fine to use but a few people on SO have said that I shouldn't use it without really specifying the reason. So I was wondering, is there a good reason?
The EOF macro doesn't signal anything, since it is just a value.
EOF will be false, and the loop will terminate.
eof()) loop doesn't work, because streams/files in C and C++ don't predict when you have reached the end of the file, but the rather indicate if you have tried to read past the end of the file.
In computing, end-of-file (EOF) is a condition in a computer operating system where no more data can be read from a data source.
You can use eof
to test for the exact condition it reports - whether you have attempted to read past end of file. You cannot use it to test whether there's more input to read, or whether reading succeeded, which are more common tests.
Wrong:
while (!cin.eof()) { cin >> foo; }
Correct:
if (!(cin >> foo)) { if (cin.eof()) { cout << "read failed due to EOF\n"; } else { cout << "read failed due to something other than EOF\n"; } }
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With