public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: paolo@gcc.gnu.org To: a.b.taylor@sympatico.ca, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, ledermg@mail.mohawkc.on.ca, nobody@gcc.gnu.org, paolo@gcc.gnu.org Subject: Re: libstdc++/8135: fixed and scientfic output with different precisions is inconsistent with standard Date: Thu, 03 Oct 2002 13:52:00 -0000 [thread overview] Message-ID: <20021003205252.18753.qmail@sources.redhat.com> (raw) Synopsis: fixed and scientfic output with different precisions is inconsistent with standard Responsible-Changed-From-To: unassigned->paolo Responsible-Changed-By: paolo Responsible-Changed-When: Thu Oct 3 13:52:51 2002 Responsible-Changed-Why: Analyzed. State-Changed-From-To: open->closed State-Changed-By: paolo State-Changed-When: Thu Oct 3 13:52:51 2002 State-Changed-Why: Not a bug. Try the following, which compares libstdc++-v3 to the letter of the standard (22.2.2.2.2,8 and 11) #include <iostream> #include <iomanip> #include <cstdio> using namespace std; const double pi = 3.1415926535, sm = 0.00004321; void experiment(); int main() { experiment(); cout.setf(ios::fixed | ios::scientific, ios::floatfield); experiment(); return 0; } void experiment() { cout << "floatfield:"; ios::fmtflags f = cout.flags(); if (f & ios::fixed) cout << " fixed"; if (f & ios::scientific) cout << " scientific"; cout << endl; for (int x = 0; x < 10; x++) { cout << x << ". " << setprecision(x) << setw(20) << pi << setw(20) << sm; if (x > 0 || (cout.flags() & ios::fixed)) printf("%20.*g%20.*g\n", x, pi, x, sm); else printf("%20g%20g\n", pi, sm); } } http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8135
next reply other threads:[~2002-10-03 20:52 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-03 13:52 paolo [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-03 12:36 a.b.taylor
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=20021003205252.18753.qmail@sources.redhat.com \ --to=paolo@gcc.gnu.org \ --cc=a.b.taylor@sympatico.ca \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=ledermg@mail.mohawkc.on.ca \ --cc=nobody@gcc.gnu.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).