[Bug libc/4943] Inconsistent rounding behaviour for sprintf and IEEE doubles

["paul at inet dot co dot za" <sourceware-bugzilla at sourceware dot org>]

------- Additional Comments From paul at inet dot co dot za  2007-09-20 14:33 -------
That was a very nice answer to get to a very real query.  Thank you.

You and Microsoft really cannot both be right about this one, you know.  Is it
really that hard to admit you are wrong?

No, Sir, I will not "go away" as you put it.  Consider for a moment the
implications:  I write an app that reports financial statements using Windows
and sprintf().  I later port the whole shananigan to Linux.  You don't need a
degree in astrophysics to guess which library will get kicked.

The current behaviour is correct only in how the FPU deals with rounding the
error at the 15'th decimal of precision.  That behaviour, and indeed the IEEE
specification has absolutely nothing to do with what printf() produces when
asked to represent a current value, which for 8 byte doubles is always stored to
15 decimals of precision, as text.

I contend that you are yourself
  a) Egotistical and
  b) an idiot.

Futhermore, you have no clue as to the damage you are causing to the credibility
of GLibC as a library, and the open source community as a whole with your
ridiculous attitude.

No.  I will not go away.  I will take this one as far as it needs to go.  I will
stick to you like a leech until you either give me a very good reason for why
GLibC differs from Microsoft, or you fix the problem.  

I am not intimidated by you or your childish responses.  If it's credibility you
think you have, let us see how well you like having your comments published.

Kindest regards


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=4943

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.