Excerpt from The C Programming Language by Kerninghan Ritchie -
*int fflush(FILE *stream) - *On an output stream, fflush causes any
buffered but unwritten data to be written; *on an input stream, the effect
is undefined*.
So fflush was never meant for stdin.
- Ravindra
On Sun, Oct 9, 2011 at
Hi,
In the following programming when i gave character input rather
than integer , the following scanf statement is not working . so i introduce
the fflush(stdin) before the last scanf statement.
But i get the same error as i before .
#includestdio.h
int
just take input a and b in one statement like this scanf(%d %d ,a ,b);
On Sun, Oct 9, 2011 at 4:50 PM, Saravanan Selvamani
saravananselvam...@gmail.com wrote:
Hi,
In the following programming when i gave character input rather
than integer , the following scanf statement is not
After scanning the variable a, you will give a whitespace
character(space,tab or newline), which will also get stored into stdin file.
So next statement will scan this whitespace character.
fflush(stdin) flushes(clears) the contents of stdin file, so this time scanf
will not get whitespace
Sorry for previous email, did not read the question properly.
Sanju
:)
On Sun, Oct 9, 2011 at 7:12 PM, Sanjay Rajpal srn...@gmail.com wrote:
After scanning the variable a, you will give a whitespace
character(space,tab or newline), which will also get stored into stdin file.
So next
these are some lines form fflush man pages
For output streams, fflush() forces a write of all user-space buffered data
for the given output or update stream via the stream's underlying write
function. *For input streams, fflush() discards any buffered data that has
been fetched from the
don't fflush(stdin) it doesn't make any sense.
fflush(stdout) and fflush(stderr) only.
On Sun, Oct 9, 2011 at 8:20 AM, Saravanan Selvamani
saravananselvam...@gmail.com wrote:
Hi,
In the following programming when i gave character input rather
than integer , the following scanf
