What's so bad about scanf anyway???

John Gordon gordon at osiris.cso.uiuc.edu
Sun Nov 11 13:25:04 AEST 1990


	Scanf() is bad because if you use it to directly get user input, and
the user types in something different than scanf() is expecting, it screws
up.  A better scheme is to store user input in an intermediate buffer and
sscanf() the buffer.



More information about the Comp.lang.c mailing list