Bug #3671
closed
floor() evaluation give incorrect result
0%
Description
Bug issue and example reported in forum post:
https://saxonica.plan.io/boards/2/topics/7116
Th example code to reproduce the problem is in the forum post., which works in Saxon-EE but gives incorrect result under Saxon-HE
An example can be: floor(-2.3) returns -2 instead of -3.
Updated by O'Neil Delpratt about 6 years ago
Equation:
floor ( ( (tag2 x tag3 x number(tag4) ) div 5 ) x 5 )
Expected result: -1.418362E7
Actual Result: -1.418361E7
Updated by O'Neil Delpratt about 6 years ago
- Status changed from New to Won't fix
- Applies to branch 9.5 added
- Applies to branch deleted (
9.8, trunk)
The bug is actually not present in Saxon 9.8 HE or EE only relevant to 9.5.
Closing bug issue.
Updated by Michael Kay about 6 years ago
So:
-
We've reproduced the problem in 9.5 under .NET.
-
It does not occur in 9.5 on the Java platform.
-
It does not occur in 9.8 on either platform.
As far as I can see, the Saxon code hasn't changed. What has changed is that we switched to a new version of IKVM when building the product. So I suspect this is an IKVM bug that has been cleared.
We no longer actively support 9.5, so we will not be back-porting any fix. (You could try rebuilding 9.5 with a newer version of IKVM if you're feeling ambitious).
Updated by Kishlay Kumar about 6 years ago
Hi O'Neil Delpratt
I have already mentioned the point about the floor() issue not present in 9.8 HE, that is the reason why we have upgraded to 9.8 HE version but we are facing another issue with this version, that is "Invalid URI" when the XSLT path contains white-spaces.
You can check the details and samples to reproduce this in the forum https://saxonica.plan.io/boards/2/topics/7116
We are happy to use 9.8 HE if this Invalid URI is fixed too.
Please let us know.
Updated by O'Neil Delpratt about 6 years ago
Sorry,
I realized your point afterwards. Please see response to the white space issue in the forum post.
Updated by Michael Kay about 6 years ago
Kishlay: we prefer to use the bug issue entries strictly to discuss the bug in question and its resolution, as a permanent record that is useful to all users of the product. We're happy to discuss with you other factors that get in your way of upgrading to a new Saxon release, but this isn't the right place for that discussion.
Please register to edit this issue
.