Printable View
while ( (letter= cin.get () ) != -1)
Would that work correctly? What I mean is the != -1 part used to exit the while loop.
I am reading this college book on C++ and they used EOF instead of -1. Which one is better? End of File just seemed harder to tell what to press to me.
EOF is very C-like...
I'd use something like:
Code:while(!cin.eof()) {
// ...
letter = cin.get();
}
Can I use -1 instead of eof?
What is the advantage of using eof instead of -1?
And, does it matter is eof is uppercase or not?
And, I don't understand what eof will do because everything I try to compile in dev C++ gives error messages and doesn't run. So I can't test things out yet.
EOF is independent of the character encoding. You don't have any guarantees that EOF will be -1 on every platform.
So I probably should not use eof but a specified # or character set that I choose.
If you want to read to the end of the file, check for stream.eof(), as was said before :)
I am just learning C++ and I have no idea what you mean by that. I am sorry.
What is meant is that if you want to read a file all the way to the end (End Of File), then you should test for end of file - not a value. As said by CB, if you test for a value, it might not be the same on every platform, machine etc. etc. By testing for eof: stream.eof(), you are actually testing for the eof.
Am I right? Or have I got the wrong end?
HD
How is the user going to know what to press to end the file? Does stream.eof() reveal it to them?
No. The file ends when it ends, i.e. no more data in it. If you want to signal EOF to an input stream, it's dependent on the OS/shell you're using. It's Ctrl-D for Unix on i386, and Ctrl-Z for DOS (I think).
Could you give a very small example of how stream.eof() is used and what the user will see?
bool basic_ios<Elem, Traits>::eof();
Returns true if the current stream has reached the end of the file and characters can no longer be read from it.
"Has reached the end of the file" is achieved in two ways: in text mode the EOF character (forgot the ASCII code), in binary mode the true end of the file as denoted by the file descriptor.
Ctrl-Z for all Microsoft consoles.Quote:
Originally posted by parksie
No. The file ends when it ends, i.e. no more data in it. If you want to signal EOF to an input stream, it's dependent on the OS/shell you're using. It's Ctrl-D for Unix on i386, and Ctrl-Z for DOS (I think).
I keep pressing Ctrl+Z in UNIX too, suspending cat. :(
Then I always get confused when I can't log out...
I use Ctrl-C to terminate things like cat on output, Ctrl-D to terminate input or logout.
cat > file
I still don't see the point of even using eof. I think it would be easier to use -1 or some letter combination to exit a loop.
Trust me, the stream knows more about its internals than you do, and it's portable.
But if you expect the user to input something on the console then of course you can choose whatever key combination you like. But NOT -1. -1 is no key combination.
Ok, say that I did use eof. Would the user always be notiifed of what to push? Or would that just be something that is learned?
He wouldn't know unless he knows his OS. The average today's windows user doesn't even know what EOF is, much less how to force it in console mode.
It depends on your input. If you need to read positive numbers from the user let him finish by entering a negative number. If you read any number let him finish by entering any character. If you read a long string where any character can occur, you're screwed ;) But you shouldn't expect users to write an essay on the console anyway. You could for example stop if the user enters an unlikely sequence, like ==&==.
If you read in a number of records which each consists of a few numbers and strings, give the user a choice between continuing and stopping between each record.
And so on. Checking for eof on console input is not a good idea. Choose a stopping method that makes sense in your context and inform the user how to use it.
That is exactly the reply I was hoping for and expecting. Thank you.