Samsung Tab3, Invite Code: KRUDCRUNCHY
2 Likes
NO FAIR he got extra!!
1 Like
Probably the same as this:
Dunno if this is that high on a priority list of fixes though (see @Spherix’s reply to Tacet for an explanation as to why it might be happening)
1 Like
Dang. I was all ready to make an Intel CPU joke (which would be older than many of the people on this forum), but Spherix had to come along and give a more reasonable explanation.
1 Like
So why not share it anyway?
220% wasnt enough really.
Since you asked…
The Pentium FDIV bug was a computer bug that affected the floating point unit (FPU) of the early Intel Pentium processors. Because of the bug, the processor could return incorrect decimal results when dividing a number. Discovered in 1994 by Professor Thomas R. Nicely at Lynchburg College,[1] Intel attributed the error to missing entries in the lookup table used by the floating-point division circuitry.[2]
The severity of the FDIV bug is debated. Intel, producer of the affected chip, claims that the common user would experience it once every 27,000 years while IBM, manufacturer of a chip competing with Intel’s Pentium, claims that the common user would experience it once every 24 days. Though rarely encountered by most users (Byte magazine estimated that 1 in 9 billion floating point divides with random parameters would produce inaccurate results),[3] both the flaw and Intel’s initial handling of the matter were heavily criticized by the tech community. The man who found the bug points out that since it went unnoticed for a year in a popular product, that likely indicates that the bug was less harmful than IBM suggested.
In December 1994, Intel recalled the defective processors. In January 1995, Intel announced “a pre-tax charge of $475 million against earnings, ostensibly the total cost associated with replacement of the flawed processors.”
220.00000000…3% sounds like a mismatch in precision while doing a numeric conversion from a floating point number to a floating point variable containing an integer. The ‘3’ at the end makes me think the original floating point was irrational, as if multiplication by 1/3 (.3333333333333) was involved.
Flash doesn’t do non-Integer math properly. It never has. I had to deal with that Macromedia (now Adobe) silliness for 15+ years.
The real issue is not trying to smash the underlying problem because it’s likely out of the control of the developers… it boils down to an incorrectly formatted text element, that’s it.
1 Like