Saxon

This arises from https://stackoverflow.com/questions/64609315/how-to-get-warnings-from-schema-aware-xslt-using-saxon-api/64611632?noredirect=1#comment114245448_64611632

Actually, looking at the Java code, I'm not sure that setting FastCompilation to false achieves much. It sets the optimizer options to be what they are at Configuration level, which I would think has JIT=true.

Michael Kay wrote:

Let's add some tests to see if the property actually has any effect...

I'll do this on the Java side.

I will port junit tests to nunit when ready.

Also, is it possible to retain the misspelt name as a deprecated synonym in 10.x (dropping it on trunk)?

Added back the property, with obsolete status added.

Two other observations:

• XsltCompiler on .NET lacks the method XsltCompiler.setJustInTimeCompilation()

• XsltCompiler on .NET has a method GetUnderlyingCompilerInfo(), perhaps it should also have GetUnderlyingXsltCompiler() - and perhaps this applies to all the C# classes that are layered on top of Java s9api classes.

Michael Kay wrote:

Two other observations:

• XsltCompiler on .NET lacks the method XsltCompiler.setJustInTimeCompilation()

Method added.

• XsltCompiler on .NET has a method GetUnderlyingCompilerInfo(), perhaps it should also have GetUnderlyingXsltCompiler() - and perhaps this applies to all the C# classes that are layered on top of Java s9api classes.

I have added the underlying implementation object where required. Some class have the underlying object already as the property Implementation.