Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!att!ima!dirtydog!karl
From: karl@ima.isc.com (Karl Heuer)
Newsgroups: comp.lang.c
Subject: Re: What's so bad about scanf anyway???
Message-ID: <1990Nov14.011717.14276@dirtydog.ima.isc.com>
Date: 14 Nov 90 01:17:17 GMT
References: <16582@netcom.UUCP> <VXogs2w163w@cybrspc> <1990Nov12.050450.7194@Solbourne.COM> <1793@b15.INGR.COM> <48257@cornell.UUCP>
Sender: news@dirtydog.ima.isc.com (NEWS ADMIN)
Reply-To: karl@ima.isc.com (Karl Heuer)
Organization: Interactive Systems
Lines: 8

In article <48257@cornell.UUCP> hilfingr@cs.cornell.edu (Paul N. Hilfinger) writes:
>2. Several contributors have suggested the use of sscanf after using
>fgets.  This has problems, since sscanf won't tell you where in its
>input string it stopped reading.

Fixed in ANSI C, via the `%n' specifier.

Karl W. Z. Heuer (karl@ima.isc.com or uunet!ima!karl), The Walking Lint