public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/12437] scanf behavior differs from WG14/N1256 Committee Draft — Septermber 7, 2007 Date: Fri, 07 Oct 2011 04:24:00 -0000 [thread overview] Message-ID: <bug-12437-131-G8fsh1TmU1@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-12437-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=12437 Rich Felker <bugdal at aerifal dot cx> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |bugdal at aerifal dot cx Resolution|INVALID | --- Comment #2 from Rich Felker <bugdal at aerifal dot cx> 2011-10-07 04:24:05 UTC --- This bug is valid. Nobody is claiming scanf should pushback two characters, but it needs to report a matching failure rather than accepting "100e" as if it were a valid floating point representation. The C standard could not be more explicit on this matter. -- 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.
next prev parent reply other threads:[~2011-10-07 4:24 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-25 20:46 [Bug libc/12437] New: " hjl.tools at gmail dot com 2011-01-25 22:49 ` [Bug libc/12437] " drepper.fsp at gmail dot com 2011-10-07 4:24 ` bugdal at aerifal dot cx [this message] 2012-02-21 2:20 ` [Bug stdio/12437] " jsm28 at gcc dot gnu.org 2012-09-28 4:53 ` bugzilla-mail-box at yandex dot ru 2012-09-28 12:27 ` bugdal at aerifal dot cx 2014-06-27 14:00 ` fweimer at redhat dot com 2014-06-27 14:00 ` fweimer at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-12437-131-G8fsh1TmU1@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).