Hmm, someone typed this function below and I don't understand it.
2 questions:Code:void clear_buffer(void) { int ch; while((ch = getchar()) != '\n' && ch != EOF); }
1. Why does it clear the buffer? I mean, it's just a while loop that *I have no idea what is does, lol* - so please explain me what it does either
2. Why did he type void function(void) - why is the parameter is void? I've seen it before and never actually understood what it does.
When do you plan to read the tutorials?
Some functions might leave characters unread in the stdin buffer where input from user is normally stored when you key.Originally Posted by eXeCuTeR
1. Why does it clear the buffer? I mean, it's just a while loop that *I have no idea what is does, lol* - so please explain me what it does either
while((ch = getchar()) != '\n' && ch != EOF);
will continually read, by virtue of the loop, one character at a time until encounters the "enter key" or '\n' "new line" or the "End Of File" whichever is first. Clearing whatever was left in the stdin, or not. But the idea is to have a clean buffer for new functions to be call for user input.
Functions are designed to return something and to accept some parameters inside the parenthesis. If the written prototype is: clear_buffer() the compiler makes some decisions about what is reading and will interprete as int clear_buffer( void ). Just because is not explicitly written doesn't mean is not there.
Therefore if you want a function that doesn't return any value and doesn't accept any parameters is necessary to write void function() and even better void function ( void )
Last edited by Aia; 11-24-2007 at 11:32 PM.
I don't understand the EOF.
What is it exactly?
I know it's End Of File but it doesn't say to me anything.
And thanks
BTW,
Why while?
EOF is a constant that getchar() (and others) returns when it has reached the end of the file.
the value of EOF is implementation defined.
EOF is a macro.
EOF has a value outside the range of a char, so you need an int when you store the return value of getchar and check if there is an error conditon.
What file and what is stdin?
For all intents and purposes stdin is treated like a file* because it works with parts of the I/O library and uses all of its constants. EOF is one of these. EOF is defined by the C standard as a negative number, signaling the end of a file. Functions that read stuff from files can return this when there is nothing left to read, but there are a few exceptions (i.e. fread, fwrite). That's all you need to know about EOF.
*But it is _not_ a file. Basically, don't try anything like fclose or freopen on stdin or any other std handles. Just read from stdin, write to stdout, etc. and be happy.
The one you happen to be reading from, or even standard input.What file
Standard input, commonly representing keyboard input at the command line. EOF in such a case is usually triggered by some special key combination, e.g., CTRL + Z or CTRL + D.what is stdin?
Look up a C++ Reference and learn How To Ask Questions The Smart Way
But why (ch = getchar()) != EOF?
and why I need stdin for if I could create my own FILE * and I could do much more things with it?
Because the input buffer has no more contents when EOF is returned.But why (ch = getchar()) != EOF?
You do not need stdin, unless you want to read from standard input.and why I need stdin for if I could create my own FILE * and I could do much more things with it?
Look up a C++ Reference and learn How To Ask Questions The Smart Way
Standard input? I don't understand what's this standard input.
Sorry and thanks
Generally, keyboard input at the command line.Standard input? I don't understand what's this standard input.
Look up a C++ Reference and learn How To Ask Questions The Smart Way
there's no int argc, char *argv[] in some programs I see that use stdin.
Indeed, for command line arguments are optional.there's no int argc, char *argv[] in some programs I see that use stdin.
By the way, have you ever written a "hello world" program for the command line?
Look up a C++ Reference and learn How To Ask Questions The Smart Way
No, not argv/argc - I think that Laserlight meant the "command prompt", rather than "command line arguments".
stdin is whatever the input is when you use getchar() - it's commonly "the keyboard", but it could be a file if you do something like "a.exe < somefile" - in this case, the stdin is redirected and comes from "somefile" instead of the keyboard.
The same applies to "stdout", which is where printf() goes - it's usually the "console", but sometimes it can be a file, e.g. "a.exe > someoutfile" - this writes the output of your application to "someoutfile".
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
