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 29241 - [FO31] Minor inconsistencies in argument names
Summary: [FO31] Minor inconsistencies in argument names
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 3.1 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: P2 editorial
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-26 09:18 UTC by Tim Mills
Modified: 2016-03-22 09:58 UTC (History)
0 users

See Also:


Attachments

Description Tim Mills 2015-10-26 09:18:50 UTC
Could the second argument $index be renamed to $position, 

    array:get($array as array(*), $index as xs:integer) as item()*

to match other function signatures

    array:remove($array as array(*), $position as xs:integer) as array(*)
amd
    array:insert-before($array	 as array(*), $position	 as xs:integer, $member	 as item()*) as array(*)


Similarly, the first argument of

array:sort($input as array(*)) as array(*)
array:sort($input	 as array(*), $key	 as function(item()*) as xs:anyAtomicType*) as array(*)
array:flatten($input as item()*) as item()*

be renamed to $array, matching the rest of the "array" functions.

While these are trivial changes, it might be beneficial for IDE users.
Comment 1 Michael Kay 2015-12-16 12:34:57 UTC
I have made these editorial changes. It never occurred to me that the choice of argument names might affect anything outside the specification itself (I probably wouldn't have used "appendage" otherwise!), but I guess you are right.