[jira] [Updated] (XALANJ-2747) xalan-j xpath3 built-in function calls, should allow literal sequence and array arguments
"Mukul Gandhi (Jira)" <[email protected]> Sat, 28 Feb 2026 15:04:00 +0000 (UTC)
| Newsgroups | gmane.text.xml.xalan.devel |
|---|---|
| Message-ID | <[email protected]> |
[ https://issues.apache.org/jira/browse/XALANJ-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mukul Gandhi updated XALANJ-2747:
---------------------------------
Fix Version/s: xslt3.0_alpha1
> 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
> Fix For: xslt3.0_alpha1
>
>
> 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)