Path: utzoo!attcan!uunet!pilchuck!ssc!mcgp1!brat!donn
From: donn@brat.UUCP (Donn Pedro)
Newsgroups: comp.lang.c
Subject: Re: Problems with scanf()
Message-ID: <324@brat.UUCP>
Date: 26 Oct 90 01:55:13 GMT
References: <1990Oct12.154156.25096@murdoch.acc.Virginia.EDU> <1990Oct20.001637.28244@unislc.uucp>
Distribution: na
Organization: Tandemonium, Kent, WA
Lines: 18

In article <1990Oct20.001637.28244@unislc.uucp>, ttobler@unislc.uucp (Trent Tobler) writes:
> 
> [many comments on the evils of scanf]
> 
> People, scanf is not BAD, [ rest of the sensible talk deleted for brevity.]

We discussed scanf() in my C course today.  The insructor basically said
to be cautious of scanf() but not fearful to use it.  He said it can be
a very useful and powerful tool *as long as* you understand it's 
limitations and foibles.

To paraphrase:

	Commnads don't kill data.  People kill data.


      Donn F Pedro ....................a.k.a. uunet!nwnexus!mcgp1!brat!donn
         else:  {the known world}!uunet!nwnexus!mcgp1!brat!donn