Project

Profile

Help

Support #6038

closed

Some undocumented or unintended version 4 support in Saxon 11.5 HE and 12.2 HE with XQuery?

Added by Martin Honnen over 1 year ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Features new in 4.0
Sprint/Milestone:
-
Start date:
2023-05-13
Due date:
% Done:

0%

Estimated time:
Legacy ID:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:

Description

I thought any (experimental) XPath 4.0, XQuery 4.0 and XSLT 4.0 support is restricted to PE and EE but somehow I find that both Saxon HE 11.5 and 12.2 from the command line execute XQuery 4.0 code using the -> compact function syntax just fine e.g.

xquery version "4.0";

for-each-pair((1 to 5), (1 to 5) => reverse(), ->($a, $b) {$a + $b})
PS C:\Users\marti\OneDrive\Documents\XQuery\XQuery4\thin-arrow-operator> type .\thin-arrow-function1.xq
xquery version "4.0";

for-each-pair((1 to 5), (1 to 5) => reverse(), ->($a, $b) {$a + $b})
PS C:\Users\marti\OneDrive\Documents\XQuery\XQuery4\thin-arrow-operator> java -cp 'C:\Program Files\Saxonica\SaxonHE11-5J\saxon-he-11.5.jar' net.sf.saxon.Query -t thin-arrow-function1.xq
SaxonJ-HE 11.5 from Saxonica
Java version 1.8.0_372
Analyzing query from thin-arrow-function1.xq
Analysis time: 343.6697 milliseconds
<?xml version="1.0" encoding="UTF-8"?>6 6 6 6 6Execution time: 29.0722ms
Memory used: 50Mb
PS C:\Users\marti\OneDrive\Documents\XQuery\XQuery4\thin-arrow-operator> java -cp 'C:\Program Files\Saxonica\SaxonHE12-2J\saxon-he-12.2.jar' net.sf.saxon.Query -t thin-arrow-function1.xq
SaxonJ-HE 12.2 from Saxonica
Java version 1.8.0_372
Analyzing query from thin-arrow-function1.xq
Analysis time: 342.058 milliseconds
<?xml version="1.0" encoding="UTF-8"?>6 6 6 6 6Execution time: 48.3746ms
Memory used: 53Mb

Undocumented or unintended?

Actions #1

Updated by Norm Tovey-Walsh over 1 year ago

Undocumented or unintended?

“Yes.”

That’s definitely unintended. I’ve got a couple of open issues for
places where I think HE is doing things that should only be available in
PE and EE. I’d expect those issues to be fixed in a future release, but
chasing them down isn’t my highest priority. :-)

Be seeing you,
norm

--
Norm Tovey-Walsh
Saxonica

Actions #2

Updated by Michael Kay over 1 year ago

Yes, the checking is a little ad-hoc; the checking for a license file is present on some paths and not others. Also, some features are implemented in code that is present in com.saxonica code which is excluded from the HE product, other features are implemented in shared code.

Actions #3

Updated by Michael Kay over 1 year ago

Partially fixed.

Actions #4

Updated by Michael Kay over 1 year ago

  • Status changed from New to Closed

Please register to edit this issue

Also available in: Atom PDF