Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!ico!haddock!karl
From: karl@haddock.ima.isc.com (Karl Heuer)
Newsgroups: comp.std.c
Subject: scanf pushback (was: X3J11 Pleasanton meeting summary)
Keywords: X3J11 Pleasanton meeting C standard interpretations
Message-ID: <18454@haddock.ima.isc.com>
Date: 8 Oct 90 18:50:40 GMT
References: <13996@smoke.BRL.MIL> <26889@mimsy.umd.edu> <14057@smoke.BRL.MIL>
Reply-To: karl@kelp.ima.isc.com (Karl Heuer)
Organization: Interactive Systems, Cambridge, MA 02138-5302
Lines: 11

In article <14057@smoke.BRL.MIL> gwyn@smoke.BRL.MIL (Doug Gwyn) writes:
>I think the main motivation was the abhorrence many members have to
>the idea that when scanning an input stream they might have to "push
>back" several characters.

But even with this ruling, they still have to be able to push back two
characters: one via scanf(), and a second one via ungetc().  Adding this
second slot is the hard part--once you've solved that, extending it to
the four (or whatever) slots needed by the "smarter scanf" is easy.

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