This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20073 - castable-expression tests have wrong expected result
Summary: castable-expression tests have wrong expected result
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3 & XPath 3 Test Suite (show other bugs)
Version: Working drafts
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: O'Neil Delpratt
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-25 06:38 UTC by Markos Zaharioudakis
Modified: 2012-12-09 19:26 UTC (History)
1 user (show)

See Also:

Attachments

Description Markos Zaharioudakis 2012-11-25 06:38:25 UTC 
The following test cases:

cbcl-castable-decimal-007
cbcl-castable-decimal-008
cbcl-castable-decimal-009
cbcl-castable-decimal-010
cbcl-castable-integer-001
cbcl-castable-integer-002
cbcl-castable-integer-003
cbcl-castable-integer-004

have "fase" as their expected result. I don't understand why. I think the expected result should be "true", assuming the implementation does not pose any upper bounds on integers and decimals.
Comment 1 Michael Kay 2012-12-09 19:26:09 UTC 
I have changed these tests to allow either true or false. An implementation is allowed to return false because the supplied value might be outside the limits of an integer/decimal; it is also allowed to return true, because the limits are implementation-defined.