public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 20804] Misbehavior of printf %e format. Date: Mon, 13 Aug 2012 20:58:00 -0000 [thread overview] Message-ID: <20120813205744.639032FB082E@mail.ecoscentric.com> (raw) In-Reply-To: <bug-20804-13@http.bugs.ecos.sourceware.org/> Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=20804 Jonathan Larmour <jifl@ecoscentric.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jifl@ecoscentric.com --- Comment #7 from Jonathan Larmour <jifl@ecoscentric.com> 2012-08-13 21:57:40 BST --- Yes I object, looking at the patch, I don't think it's right. I don't see the reason for this: - if ((ch != 'g' && ch != 'G') || (flags&ALT)) + if (ch == 'f') The precision (e.g. 18 in "%.18f") is defined as the number of digits to appear after the radix character for e, E, and f conversions, or the maximum number of significant digits for g and G conversions. I don't see how the above can fit into that, nor do I have confidence that the ALT flag ('#') is correctly handled. And Bernd seems to have doubts too - he says in bug 1001490 it's only an interim solution. I don't want to be swapping one set of problems for a different but now less known set of problems. Unfortunately I don't have the time to look at this at the moment as I'm leaving on holiday soon and have to finish work things off. But I'd want to see confidence that the changes made are correct before committing. Jifl -- Configure bugmail: http://bugs.ecos.sourceware.org/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:[~2012-08-13 20:58 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-20804-13@http.bugs.ecos.sourceware.org/> 2012-08-08 18:51 ` bugzilla-daemon 2012-08-09 10:58 ` bugzilla-daemon 2012-08-12 18:07 ` bugzilla-daemon 2012-08-13 20:58 ` bugzilla-daemon [this message] 2012-08-14 6:51 ` bugzilla-daemon 2012-08-14 7:41 ` bugzilla-daemon 2012-08-14 8:31 ` bugzilla-daemon 2012-08-14 8:50 ` bugzilla-daemon 2012-08-14 9:15 ` bugzilla-daemon 2012-08-14 10:48 ` bugzilla-daemon 2012-08-14 12:34 ` bugzilla-daemon [not found] <bug-20804-777@http.bugs.ecos.sourceware.org/> 2012-08-08 18:51 ` bugzilla-daemon 2012-08-09 10:58 ` bugzilla-daemon 2012-08-12 18:07 ` bugzilla-daemon 2012-08-13 20:58 ` bugzilla-daemon 2012-08-14 6:51 ` bugzilla-daemon 2012-08-14 7:41 ` bugzilla-daemon 2012-08-14 8:31 ` bugzilla-daemon 2012-08-14 8:50 ` bugzilla-daemon 2012-08-14 9:15 ` bugzilla-daemon 2012-08-14 10:48 ` bugzilla-daemon 2012-08-14 12:34 ` bugzilla-daemon [not found] <bug-20804-776@http.bugs.ecos.sourceware.org/> 2012-08-08 18:51 ` bugzilla-daemon
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=20120813205744.639032FB082E@mail.ecoscentric.com \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-bugs@ecos.sourceware.org \ /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).