Xref: utzoo comp.std.c:3357 comp.lang.c:30195
Path: utzoo!utgpu!watserv1!watmath!att!tut.cis.ohio-state.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!srhqla!demott!kdq
From: kdq@demott.COM (Kevin D. Quitt)
Newsgroups: comp.std.c,comp.lang.c
Subject: Re: Explain this sscanf behavior.
Keywords: sscanf ANSI
Message-ID: <376@demott.COM>
Date: 7 Jul 90 18:31:19 GMT
References: <1990Jul6.181830.2549@tc.fluke.COM>
Reply-To: kdq@demott.COM (Kevin D. Quitt)
Followup-To: comp.std.c
Organization: DeMott Electronics Co., Van Nuys CA
Lines: 31

In article <1990Jul6.181830.2549@tc.fluke.COM> mason@tc.fluke.COM (Nick Mason) writes:
>
>I tried this with 3 different compilers and got the following:
>
>compiler A:
>
>	x=1   a=123  b=3
>	x=1   a=123  b=3
>
>compiler B:
>
>	x=1   a=123  b=3
>	x=1   a=123  b=4  <-- yes 4.
>
>compiler C:
>
>	x=1  a=123  b=3
>	x=1  a=123  b= -99
>

    I'm confused by example C: where did it get the old value of b? BTW,
Microsoft C and cc on Motorola Delta 3x00 agree with A, and gnu's gcc
coredumps. 

-- 
 _
Kevin D. Quitt         demott!kdq   kdq@demott.com
DeMott Electronics Co. 14707 Keswick St.   Van Nuys, CA 91405-1266
VOICE (818) 988-4975   FAX (818) 997-1190  MODEM (818) 997-4496 PEP last

                96.37% of all statistics are made up.