W3C home > Mailing lists > Public > public-qt-comments@w3.org > December 2004

RE: [F&O] op:to doesn't match language specification

From: Ashok Malhotra <ashok.malhotra@oracle.com>
Date: Wed, 15 Dec 2004 17:28:07 -0800
To: Sarah Wilkin <swilkin@apple.com>, public-qt-comments@w3.org
Message-ID: <20041215172807929.00000001764@amalhotr-pc>

If you notice, none of the op: functions in the F&O allow the empty sequence as argument even though the corresponding operator does.  This is because the empty sequence argument to operators is handled at the language level and never makes it down to the function. 

All the best, Ashok

> -----Original Message-----
> From: public-qt-comments-request@w3.org 
> [mailto:public-qt-comments-request@w3.org] On Behalf Of Sarah Wilkin
> Sent: Wednesday, December 15, 2004 4:32 PM
> To: public-qt-comments@w3.org
> Subject: [F&O] op:to doesn't match language specification
> In the October 04 language specification op:to was changed to 
> have optionally have empty operands:
> "Each of the operands of the to operator is converted as 
> though it was an argument of a function with the expected 
> parameter type xs:integer?. 
> If either operand is an empty sequence, or if the integer 
> derived from the first operand is greater than the integer 
> derived from the second operand, the result of the range 
> expression is an empty sequence..."
> Which means in F&O the signature
> op:to($firstval as xs:integer, $lastval as xs:integer) as xs:integer*
> should be:
> op:to($firstval as xs:integer?, $lastval as xs:integer?) as 
> xs:integer*
> --Sarah
Received on Thursday, 16 December 2004 01:29:13 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:22 UTC