INFO: Next scanf/fscanf Apparently Is Skipped During Run TimeLast reviewed: September 2, 1997Article ID: Q42075 |
The information in this article applies to:
SUMMARYWhen a function of the scanf() family reads a white-space character--blank (' '), tab ('\t'), or newline ('\n')--it does not ordinarily store that character into the location provided by the argument pointer. However, as documented in the Microsoft C Run-Time Library Reference, if the %c type field format specifier is used, the scanf() functions will store a white- space character. This behavior can cause unexpected results.
MORE INFORMATIONAfter the first character is read in the sample code below, the following white-space character that is still in the internal buffer for stdin is read and stored by the second scanf(). This effectively causes the second prompt to be skipped (the message is printed, but the program does not wait to accept a character). To obtain the desired behavior, use the format specifier %1s instead of %c. Don't forget to pass scanf() an array of two at least two characters, because the scanf() family will also store a terminating character ('\0') when "s" is used for the type field format. Alternatively, the fflush() function can be used to flush all characters, including white-spaces, out of the specified buffer after each scanf() or fscanf(). Use flushall() to flush all file buffers.
MORE INFORMATION
Sample Code
/* Compile options needed: none */ #include <stdio.h> void main() { char a,b[2]; do { printf( "Enter a single character\n" ); scanf( "%c", &a ); printf( "Enter another character\n" ); scanf( "%c", b ); } while ( a != 'y' ); } Keywords : CRTIss kbcode kbfasttip Version : MS-DOS:6.0,6.00a,6.00ax,7.0; WINDOWS:1.0,1.5; WINDOWS NT:1.0,2.0,2.1,4.0,5.0 Platform : MS-DOS NT WINDOWS Issue type : kbinfo |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |