View Single Post
  #7 (permalink)  
Old September 9th, 2019, 04:25 AM
mhkay's Avatar
mhkay mhkay is offline
Wrox Author
Points: 18,481, Level: 59
Points: 18,481, Level: 59 Points: 18,481, Level: 59 Points: 18,481, Level: 59
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Apr 2004
Location: Reading, Berks, United Kingdom.
Posts: 4,960
Thanks: 0
Thanked 292 Times in 287 Posts
Default

Actually, it's not clear to me why Saxon should produce this message. In Saxon 9.9, we follow the XSLT 3.0 and XPath 3.1 rules whatever the stylesheet version says. In earlier releases we try to enforce XSLT 2.0 restrictions if the stylesheet specifies version="2.0". If you really want to write 2.0-conformant code, then (a) you can't use this regex, and (b) you'll need to use an earlier Saxon release that still has XSLT 2.0 support in order to ensure that any accidental use of 3.0 constructs is rejected. Otherwise, I suggest setting version="3.0" on the xsl:stylesheet element.
__________________
Michael Kay
http://www.saxonica.com/
Author, XSLT 2.0 and XPath 2.0 Programmer\'s Reference
Reply With Quote