This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug stdio/12437] scanf behavior differs from WG14/N1256 Committee Draft â Septermber 7, 2007
- From: "bugzilla-mail-box at yandex dot ru" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Fri, 28 Sep 2012 04:53:12 +0000
- Subject: [Bug stdio/12437] scanf behavior differs from WG14/N1256 Committee Draft â Septermber 7, 2007
- Auto-submitted: auto-generated
- References: <bug-12437-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12437
gmper <bugzilla-mail-box at yandex dot ru> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugzilla-mail-box at yandex
| |dot ru
--- Comment #3 from gmper <bugzilla-mail-box at yandex dot ru> 2012-09-28 04:53:12 UTC ---
Why shouldn't the scanf() function read "100" from "100e" ?
If it shouldn't read even "100" from "100e" (according to the standard), what
it should leave in the input stream after that matching failure ? What is the
next character during the next call of a reading function ?
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.