What's so bad about scanf anyway???

Richard Caley rjc at uk.ac.ed.cstr
Mon Nov 12 12:23:56 AEST 1990


In article <VXogs2w163w at cybrspc> roy%cybrspc at cs.umn.edu (Roy M. Silvernail) writes:

    The problem with scanf() is that it can behave unpredictably when you
    give it badly formatted input. It's better, IMHO, to gets() a whole
    line, check its validity and _then_ sscanf() it into the target
    variables.

Maybe it was just a typo, but repeat after me

	`GETS is EVIL'

This has been un unpayed anouncement by paranoids anonymous.

--
rjc at uk.ac.ed.cstr			_O_
					 |<



More information about the Comp.lang.c mailing list