Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: Explain this sscanf behavior.
Keywords: sscanf ANSI
Message-ID: <13320@smoke.BRL.MIL>
Date: 8 Jul 90 06:26:34 GMT
References: <1990Jul6.181830.2549@tc.fluke.COM> <376@demott.COM>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 6

In article <376@demott.COM> kdq@demott.COM (Kevin D. Quitt) writes:
>    I'm confused by example C: where did it get the old value of b?

I think we have to assume that
	b = -99;
was also supposed to be performed before the second sscanf().