[
https://issues.apache.org/jira/browse/XALANJ-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Gandhi updated XALANJ-2747:
---------------------------------
Summary: xalan-j xpath3 built-in function calls, should allow literal
sequence and array arguments (was: xalan-j xpath3 function calls, should allow
literal sequence and array arguments)
> xalan-j xpath3 built-in function calls, should allow literal sequence and
> array arguments
> -----------------------------------------------------------------------------------------
>
> Key: XALANJ-2747
> URL: https://issues.apache.org/jira/browse/XALANJ-2747
> Project: XalanJ2
> Issue Type: Task
> Security Level: No security risk; visible to anyone(Ordinary problems in
> Xalan projects. Anybody can view the issue.)
> Components: Xalan-interpretive, XPath, XPath-function
> Reporter: Mukul Gandhi
> Assignee: Mukul Gandhi
> Priority: Major
>
> It think, that it'll be useful to enhance XPath 3.1 function call
> invocations, to allow literal sequence constructor and array expressions, as
> also suggested within few examples within XPath 3.1 F&O spec as follows:
> fn:for-each(("john", "jane"), function($x) { fn:string-to-codepoints($x) })
> // this is slight variation from the example provided in XPath 3.1 F&O spec
> spec. But this example is a correct XPath 3.1 function call.
> array:for-each-pair(["A", "B", "C"], [1, 2, 3], function($x, $y) { array {$x,
> $y}})
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
