I_love_tigersugar's blog

Printing double in C++
By I_love_tigersugar, 9 years ago, In English

Hi everyone!

Today, I found some problems while trying to print a double values in C++. Below is my code:

#include<bits/stdc++.h>
using namespace std;
int main(void) {
    double x=1.0/3000;
    printf("%.7lf\n",x);
    return 0;
}

When I compile this code using command mingw32-g++.exe -O2 -Wl,--stack=268435456 -DSKY, I saw 0.0003333. However, after changed to mingw32-g++.exe -O2 -std=c++11 -Wl,--stack=268435456 -DSKY (include C++11), I saw 0.0000000.

I uss Windows 8 and my g++ version is:

C:\Program Files (x86)\CodeBlocks\MinGW\bin>"mingw32-g++.exe" --version
mingw32-g++.exe (tdm-1) 4.7.1
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Has anyone ever met this problem? What is the solution to avoid this?

I'm looking forward to your answers. Thank you :D

  • Vote: I like it
  • +29
  • Vote: I do not like it

»
9 years ago, # |
  Vote: I like it -33 Vote: I do not like it

cout works fine

→ Reply
»
9 years ago, # |
  Vote: I like it +52 Vote: I do not like it

Have you also tried %f ?

All these double type printing is very confusing in C++. You can see this question on Stackoverflow:

  • for scanf: %f is float, %lf is double, %Lf is long double
  • for printf: %f is double, %Lf is long double.

This is C99 standard. Finding what is the current standard requires some more efforts, so I'll stop here. Anw, moral of the story is trying your best to avoid printf, scanf when dealing with floating types.

→ Reply
»
9 years ago, # |
  Vote: I like it -54 Vote: I do not like it

No g++, no problems. MS C++ works fine.

→ Reply
»
9 years ago, # |
  Vote: I like it -10 Vote: I do not like it

I use %lf without any problems. I see many C++-coders who use %lf without any problems, too. Recently, I use cout and I notice that the running time is almost the same. Thus, I think cout may be the solution for you.

→ Reply
»
9 years ago, # |
  Vote: I like it 0 Vote: I do not like it

If you're using mingw with c++11 support, use %f for printf, %lf for scanf.

Comments about following standard are irrelevant because Windows doesn't anyway.

→ Reply
»
9 years ago, # |
  Vote: I like it +8 Vote: I do not like it

cout<<fixed<<setprecision(10); and you can forget what is f, lf, Lf or maybe lF, LF and shit. Moreover no longer any problems with stupid 0.000000

→ Reply
  • »
    »
    9 years ago, # ^ |
      Vote: I like it +74 Vote: I do not like it

    Unless you printing fkn long double on fkn mingw at NEERC

    → Reply
    • »
      »
      »
      9 years ago, # ^ |
        Vote: I like it 0 Vote: I do not like it

      Is this a case in both iostream and cstdio? I recall one contest in gym when my team got one task accepted after contest and only needed change was to print double instead of long double, however I don't remember whether we were using iostream or cstdio.

      → Reply
      • »
        »
        »
        »
        9 years ago, # ^ |
          Vote: I like it 0 Vote: I do not like it

        Well, I believe with both.

        As far as I remember problem is that version of MinGW used input/output from MS libraries which doesn't have functions for printing long double(which is equal to double in MSVC)

        → Reply
»
9 years ago, # |
  Vote: I like it 0 Vote: I do not like it

I would strongly recommend to use this version of printf on Windows: http://sourceforge.net/p/mingw-w64/wiki2/gnu%20printf/ By default printf(and scanf) on Win32 is something very strange and non-standard

→ Reply
  • »
    »
    9 years ago, # ^ |
      Vote: I like it 0 Vote: I do not like it

    It's ten times slower (not kidding) than 'standard' printf, isn't it?

    By the way, the page says that problem happens on Windows XP or earlier, which should already be buried.

    → Reply