This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
http://www.w3.org/TR/xquery-operators/#func-numeric-integer-divide says: If the divisor is (positive or negative) zero, then an error is raised [err:FOAR0001]. If either operand is NaN or if $arg1 is INF or -INF then an error is raised [err:FOAR0002]. As such the following tests should expect FOCA0002 rather than FOAR0002. K-NumericIntegerDivide-31.xq K-NumericIntegerDivide-32.xq K-NumericIntegerDivide-33.xq K-NumericIntegerDivide-34.xq Thanks, Marc
Hi Marc, I'm having a hard time following here. Here's the queries for the tests: K-NumericIntegerDivide-31: 1 idiv xs:float("NaN") K-NumericIntegerDivide-32: xs:float("NaN") idiv 1 K-NumericIntegerDivide-33: xs:float("INF") idiv xs:float(3) K-NumericIntegerDivide-34: xs:float("-INF") idiv xs:float(3) All these four currently expect FOAR0002, only. In the first two, one of the operands is NaN, and in the second two one of the operands is negative/positive infinity. Therefore, I find FOAR0002 justified, because: "If either operand is NaN or if $arg1 is INF or -INF then an error is raised [err:FOAR0002]." But that's exactly what you quoted, so I'm confused. None of the operands are "(positive or negative) zero" so FOAR0001 is ruled out. How do you reach the conclusion that FOCA0002 should be issued, instead of FOAR0002? Thanks for the report. Frans
Frans, I understand you're having a hard time to understand. Don't know what I was going on in my brain, but I guess I was really confusing myself. I have marked this bug as INVALID and appologize for the "noise". Tx, Marc
No problem at all. Changing status to CLOSED.