Path: utzoo!utgpu!attcan!uunet!husc6!ukma!nrl-cmf!ames!oliveb!sun!swilson
From: swilson@sun.uucp (Scott Wilson)
Newsgroups: comp.sys.mac.programmer
Subject: Re: LSC 3.0 scanf deletes
Keywords: delete, scanf
Message-ID: <62753@sun.uucp>
Date: 4 Aug 88 05:28:28 GMT
References: <2559@pt.cs.cmu.edu> <587@helios.ee.lbl.gov> <5794@haddock.ISC.COM> <62725@sun.uucp>
Reply-To: swilson@sun.UUCP (Scott Wilson)
Organization: Sun Microsystems, Mountain View
Lines: 16

In article <62725@sun.uucp> swilson@sun.UUCP (Scott Wilson) writes:
>scanf is not a useless function!  While I believe that to approach 100%
>bullet-proof i/o you have to do everything yourself one character at a
>time, scanf is still useful.  The problem is that most people don't
>know how to use scanf.  Consider this example:

This bit was really intended to describe the usefulness of scanf on
other systems such as UNIX.  I agree that LSC's scanf leaves something
to be desired in terms of error correction.  At least the 3.0 version
is better than the 2.15 version which didn't echo what you typed (at least
that's how I remember it, I could be wrong, ever since I tried to bitch
about a bug that was my own stupidity I don't trust myself anymore).
So I guess scanf is not good for much in LSC after all.  I really wish
ANSI could do something for us here, but I'm told it doesn't.

Scott Wilson