After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 528864 - Rounding Errors in Extending Sequence of Numbers
Rounding Errors in Extending Sequence of Numbers
Status: RESOLVED DUPLICATE of bug 509965
Product: Gnumeric
Classification: Applications
Component: General
1.8.x
Other All
: Normal minor
: ---
Assigned To: Jody Goldberg
Jody Goldberg
: 684914 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-04-19 07:30 UTC by Jeffrey Drake
Modified: 2012-09-27 19:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jeffrey Drake 2008-04-19 07:30:34 UTC
Please describe the problem:

When selecting a short sequence of numbers (4,4.1,4.2) and then extending the selection to extend the sequence it will go fine for a number of items and then will have rounding errors such as 5.49999999999999 instead of 5.5. Some testing has determined that this problem can return to normal operation even with the rounding errors in the middle of the sequence. It is not guaranteed to be the same each time.

Steps to reproduce:
1. C7 = 4; C8 = 4.1; C9 = 4.2
2. Select C7 to C9
3. Extend from the bottom right going downwards. 


Actual results:
The extended sequence worked fine until it got to 5.2, which it was 5.20000000000001, 5.30000000000001, etc. In another instance, it did it at 5.5 with 5.49999999999999, 5.59999999999999, etc. One more instance repeated this but went back to normal for 10.1.

Expected results:
It should have been 5.2, 5.3, etc.

Does this happen every time?
Every time some sort of rounding error occurs, no guarantee as to complete repeatability.

Other information:
Comment 1 Morten Welinder 2008-04-19 11:38:21 UTC

*** This bug has been marked as a duplicate of 509965 ***
Comment 2 Andreas J. Guelzow 2012-09-27 19:21:14 UTC
*** Bug 684914 has been marked as a duplicate of this bug. ***