Saxonica Developer Community

2019-08-23

• 
  Michael Kay Saxon

  00:51 · Commented on issue

  My initial guess was a bit off-target, though not totally. There's some early reorganisation of the path expression going on, during the type-checking phase (and thus well before any variable inlining), when it is realised that the trail... Bug #4298: Uncaught "java.lang.UnsupportedOperationException: Cannot copy a variable reference wh...

  This problem is in 9.9 but not 9.8. I believe it may have been introduced in a recent minor release, because I believe I had been using an earlier 9.9 version without the problem.
  Execute the following legal stylesheet against any inp...
• 
  Michael Kay How extraordinary! Thanks for reducing it to such a simple repro. I imagine that the optimizer has attempted to inline the variable $node and has somehow failed to remove an existing reference to the variable. It's probably related to a ...

  19:58 · Commented on issue
• 
  Michael Kay Saxon

  22:29 · Commented on issue

  Normally you would create the Processor and this would create the Configuration automatically.
  On the Java side it's also possible to create the Configuration first, and then create a Processor over that Configuration. That doesn't ap... Bug #4295: How to set Saxon licenseFileLocation in config file programmatically

  I need to set the licenseFileLocation.
  <configuration xmlns="http://saxon.sf.net/ns/configuration"
  edition="PE"
  licenseFileLocation="file://saxon-license.lic"
  label="Saxon.Configuration....
• 
  Michael Kay No, the primary reference is from the Processor to the Configuration, and this is always established explicitly or implicitly when tbe Processor is created. The method Configuration.setProcessor() sets a field in the Configuration for th...

  22:17 · Commented on issue
• 
  Michael Kay Saxon

  11:23 · Commented on issue

  Note also `XPathSelector` and `XQueryEvaluator` both have the capability to return an `IEnumerator` (should be `IEnumerator<XdmItem>` perhaps?), rather than XdmEnumerator. I suggest we move towards returning `XdmEnumerator`, while accept... Bug #4296: XdmEnumerator on .NET

  See also issue #4290.
  The `ExtensionFunctionDefinition/ExtensionFunctionCall` inferface on .NET requires user-written code to return an `IXdmEnumerator`. However, we do not provide any useful ways of constructing an `IXdmEnumerator`; ...
• 
  Michael Kay See also issue #4290.
  The `ExtensionFunctionDefinition/ExtensionFunctionCall` inferface on .NET requires user-written code to return an `IXdmEnumerator`. However, we do not provide any useful ways of constructing an `IXdmEnumerator`; ...

  10:18 · Created issue
• 
  Michael Kay Saxon

  11:10 · Created issue

  Bug #4297 (Resolved): API Documentation of ExtensionFunction.Call() on .NET

  The API documentation of this method is incorrect (see also issue #4290). The method returns an `XdmValue`, but the description is copied from `ExtensionFunctionCall.Call()`, which returns an enumerator.
  I suggest:
  Returns: An `Xdm...

2019-08-22

• 
  Michael Kay Saxon

  23:59 · Commented on issue

  The most straightforward way is:
  ~~~
  Processor p = new Processor(true);
  p.SetProperty(Feature.LICENSE_FILE_LOCATION, saxonLicensePath)
  ~~~
  Note however that if you use a configuration file and supply it using the `Processor` con... Bug #4295: How to set Saxon licenseFileLocation in config file programmatically

  I need to set the licenseFileLocation.
  <configuration xmlns="http://saxon.sf.net/ns/configuration"
  edition="PE"
  licenseFileLocation="file://saxon-license.lic"
  label="Saxon.Configuration....
• 
  Michael Kay Saxon

  16:06 · Commented on issue

  `ExtensionFunction.Call` returns `XdmValue` and `XdmItem` is a subtype of `XdmValue`, so yes, you can return an `XdmItem`.
  The documentation of the method appears to be incorrect; it has apparently been copied from `ExtensionFunctionC... Support #4290: Custom .NET Function

  I would like to create a custom .NET extension to be used by my XSLTs. Your documentation shows how to create the C# code, but your C# code does not compile.
  Also, there are no examples showing the namespace being registered in a st...

2019-08-21

• 
  Michael Kay Saxon

  01:24 · Commented on issue

  We are discussing internally what the best way forward is to support UNC filenames on Windows (whether running Saxon on Java or .NET). The recent RFC 8089 is helpful: it describes two "non-standard" ways of representing UNC filenames as ... Bug #4280: Failure in file:base-dir(): "URI has an authority component"

  There is an issue when calling:
  ~~~ cpp
  var transformer = _xsltCompiler.Compile(new Uri(stylesheetPath)).Load();
  ~~~
  These are the following lines I have that's dealing with the file system.
  ~~~ xml
  <xsl:function name="pn:f...