14905 2011-11-22 14:42:02 +0000 [QT3] math-exp-003 2011-11-25 14:22:04 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3 & XPath 3 Test Suite Member-only Editors Drafts PC Windows NT CLOSED FIXED P2 normal --- 1 tim benjie.nguyen mike public-qt-comments oldest_to_newest 60350 0 tim 2011-11-22 14:42:02 +0000 I fail this test because our implementation gives the result as 2.718281828459045e0 Looking at the representation of the values using System.BitConverter.DoubleToInt64Bits (.NET) or java.lang.Double.doubleToRawLongBits (Java) I get: Expected result = 4613303445314885482 Actual result = 4613303445314885481 The bit pattern for System.Math.E (.NET) or java.lang.Math.E (Java) is 4613303445314885481. <test-case name="math-exp-003"> <description>Evaluate the function exp() with the argument set to 1</description> <created by="O'Neil Delpratt, Saxonica" on="2010-12-10"/> <test>math:exp(1)</test> <result> <assert-eq>2.7182818284590455e0</assert-eq> </result> </test-case> 60399 1 mike 2011-11-23 19:47:16 +0000 It appears that in Java, the expression Math.exp(1.0e0) == Math.E returns false ;-( I'm not sure exactly what the IEEE spec has to say about the required precision of the result: it needs a lot of study to decipher the meaning. Pragmatically, it would appear to make sense for our expected result to tolerate the value that the Java library delivers, as well as what would appear to be the "correct" result. So I propose to change the test to allow an epsilon variation in the result. 60401 2 mike 2011-11-23 19:59:03 +0000 Changed test to allow a variation of 1e-15 in the result. 60492 3 tim 2011-11-25 14:22:04 +0000 Confirmed fixed. Thanks.