Floating point imprecision

[hardgeus]

IMO, it's just like cout, qDebug has a default precison when print a float, and it happened to be 0.1. But it will not do any harm to your program, it's just an output, so what are u worrying about...?

What I'm worried about is that my software checks to see if the customer is underpaying. You can't have the customer give the cashier a $5 bill to pay a $10 tab. The problem is that once the amount gets large enough, there can be up to a nickel of error. So, yesterday when a customer tried to make a $13125.20 purchase, and paid exactly $13125.20 from their credit card, the software thought that he wasn't paying enough because the variable storing the amount owed was actually $13125.24.

I don't think this is just a problem with qDebug() truncating. I am rounding all of my float values to two significant digits (cents), and I use QString::number() all over my code. Now, it WILL format to just one digit if the final digit is a "0", but it doesn't just automatically truncate to .1 every time. Even qstring::number is seeing the value, which is 13125.24 as 13125.2

I considered the possibility that I am making a mistake (which of course I still may be), but if QString::number() were always truncating to .1 then my users CERTAINLY would have noticed because every total would always be even.

[jacek]

Even qstring::number is seeing the value, which is 13125.24 as 13125.2

The docs say:

QString QString::number ( double n, char f = 'g', int prec = 6 ) [static]

Here's a small test:

#include <QtDebug>
#include <QString>
 
int main()
{
   qDebug() << QString::number( 13125.24567 );
   qDebug() << "f";
   qDebug() << QString::number( 13125.24567, 'f', 1 );
   qDebug() << QString::number( 13125.24567, 'f', 2 );
   qDebug() << QString::number( 13125.24567, 'f', 3 );
   qDebug() << "g";
   qDebug() << QString::number( 13125.24567, 'g', 6 );
   qDebug() << QString::number( 13125.24567, 'g', 7 );
   qDebug() << QString::number( 13125.24567, 'g', 8 );
}

#include <QtDebug>
#include <QString>

int main()
{
   qDebug() << QString::number( 13125.24567 );
   qDebug() << "f";
   qDebug() << QString::number( 13125.24567, 'f', 1 );
   qDebug() << QString::number( 13125.24567, 'f', 2 );
   qDebug() << QString::number( 13125.24567, 'f', 3 );
   qDebug() << "g";
   qDebug() << QString::number( 13125.24567, 'g', 6 );
   qDebug() << QString::number( 13125.24567, 'g', 7 );
   qDebug() << QString::number( 13125.24567, 'g', 8 );
}

To copy to clipboard, switch view to plain text mode 

Output:

"13125.2"
f
"13125.2"
"13125.25"
"13125.246"
g
"13125.2"
"13125.25"
"13125.246"

As you can see everything depends on what you order QString::number() to do.

[hardgeus]

The docs say:

As you can see everything depends on what you order QString::number() to do.

That's the problem...What was happening is I was assigning the values I pulled from the database into my amount textbox using:

txtAmount->setText( QString::number(fValue) );

This was truncating my cents when the value got over 10,000! Then, later, when I pulled it out of the textbox, the value was wrong. I was using the qDebug() to print, and this was masking the error since it was also truncating the cents. This error ONLY occurred when values were over 10,000 (which is unusual in my app) so the problem rarely occurred.

I'm glad this was the problem. I was starting to think that I didn't understand the behavior of floating point numbers!