Article View: comp.std.c
Article #1495Re: Explain this sscanf behavior.
From: Karl Heuer
Date: Wed, 11 Jul 1990 21:45
Date: Wed, 11 Jul 1990 21:45
10 lines
919 bytes
919 bytes
In article <1666@tuvie> inst182@tuvie.UUCP (Inst.f.Techn.Informatik) writes: >To add a new variant, on a DECstation 3100 (Ultrix 2.1) both cc (1.31) and >gcc (1.37) give the following results: > x=2, a=123, b=3 > x=1, a=123, b=3 That first one has to be wrong; you can't get a return value of 2 when you only have one input format specifier (%n doesn't count). Karl W. Z. Heuer (karl@kelp.ima.isc.com or ima!kelp!karl), The Walking Lint
Technical Details
Message-ID:
<17067@haddock.ima.isc.com>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!cs.utexas.edu!usc!snorkelwacker!spdcc!ima!haddock!karlReferences:
<1990Jul6.181830.2549@tc.fluke.COM> <1666@tuvie>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!cs.utexas.edu!usc!snorkelwacker!spdcc!ima!haddock!karl From: karl@haddock.ima.isc.com (Karl Heuer) Newsgroups: comp.std.c Subject: Re: Explain this sscanf behavior. Keywords: sscanf ANSI Message-ID: <17067@haddock.ima.isc.com> Date: 11 Jul 90 21:45:24 GMT References: <1990Jul6.181830.2549@tc.fluke.COM> <1666@tuvie> Reply-To: karl@kelp.ima.isc.com (Karl Heuer) Organization: Interactive Systems, Cambridge, MA 02138-5302 Lines: 10