4244 2007-01-17 08:41:49 +0000 Static typing of K2-StringEqual-1 to 6 2007-01-22 09:01:43 +0000 1 1 1 Unclassified XML Query Test Suite XML Query Test Suite unspecified PC Windows XP CLOSED FIXED P2 normal --- 1 tim frans.englich public-qt-comments oldest_to_newest 13643 0 tim 2007-01-17 08:41:49 +0000 In static typing implementations, declarations such as: declare variable $vA as xs:string := ("B STRING", current-time(), string(<e>cont ent</e>))[1]; may fail because under the FS typing rules, the RHS is typed as the union type ( xs:string | xs:time ). (:*******************************************************:) (: Test: K2-StringEqual-1 :) (: Written by: Frans Englich :) (: Date: 2007-01-15T15:15:44+01:00 :) (: Purpose: Compare two values returned from fn:lower-case(). :) (:*******************************************************:) declare variable $vA as xs:string := ("B STRING", current-time(), string(<e>cont ent</e>))[1]; declare variable $vB as xs:string := ("b string", current-time(), string(<e>cont ent</e>))[1]; (lower-case($vA) eq lower-case($vB)) 13645 1 tim 2007-01-17 08:45:30 +0000 K2-GenCompEq-1 to 6 fail in a similar way. 13657 2 tim 2007-01-17 12:29:48 +0000 K2-compareFunc-4 to 9 have a similar problem. 13658 3 tim 2007-01-17 12:32:13 +0000 K2-CodepointEqual-1 to 6 also have this problem. 13659 4 tim 2007-01-17 12:52:11 +0000 ... and K2-ContainsFunc-1 to 6 13712 5 nick 2007-01-19 14:06:23 +0000 Not identical, but a similar problem in K2-SeqSubsequenceFunc-1 with: declare variable $start as xs:integer := (current-time(), 2)[2]; declare variable $len as xs:integer := (current-time(), 1)[2]; 13729 6 frans.englich 2007-01-21 12:45:54 +0000 A fix has been attempted in CVS, and XQTS_current.zip has been updated to contain the new change. If it can be verified that the change is correct, it would be appreciated. If this resolution is satisfiable, feel free to change status to closed. Otherwise, reopen this report. If no opinion on the resolution is expressed within two weeks, I will change status to closed. This change to this report was part of a batch-change of several reports. 13756 7 tim 2007-01-22 09:01:43 +0000 These are all now fixed. THanks.