Path: utzoo!attcan!uunet!know!zaphod.mps.ohio-state.edu!wuarchive!udel!haven!uvaarpa!murdoch!watt1.acc.Virginia.EDU!spm2d
From: spm2d@watt1.acc.Virginia.EDU (Steven Paul Miale)
Newsgroups: comp.lang.c
Subject: scanf() problems
Summary: scanf bugs
Message-ID: <1990Oct4.130831.7814@murdoch.acc.Virginia.EDU>
Date: 4 Oct 90 13:08:31 GMT
Sender: spm2d@virginia.edu
Reply-To: spm2d@watt1.acc.Virginia.EDU (Steven Paul Miale)
Distribution: na
Organization: University of Virginia
Lines: 13
Ireallyam: spm2d

Recently, I have heard that many implementations of C have a buggy version
of scanf() attached which may cause a hard drive crash; these assertations
are from the famous C authorities here in Charlottesville.
They also claim that most scanf() versions are buggy, and to use other
read commands (such as gets() ) or to write your own routines.
Is there any truth to this rumor? I have repeatedly told these few
not to blast all versions of C because a few may have bad implementations,
but they keep pestering me and I want some *real* C programmers to set
it straight.
Please E-mail me, as I usually do not keep up with this newsgroup.
---
Steven Miale
spm2d@virginia.edu