Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!julius.cs.uiuc.edu!ux1.cso.uiuc.edu!osiris.cso.uiuc.edu!gordon
From: gordon@osiris.cso.uiuc.edu (John Gordon)
Newsgroups: comp.lang.c
Subject: Re: What's so bad about scanf anyway???
Message-ID: <1990Nov11.022504.5335@ux1.cso.uiuc.edu>
Date: 11 Nov 90 02:25:04 GMT
References: <16582@netcom.UUCP>
Sender: news@ux1.cso.uiuc.edu (News)
Organization: University of Illinois at Urbana
Lines: 5


	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.