Bug #4816
closed
Misspelt property name: XsltCompiler.FastCompliation (.NET)
Applies to branch:
10, trunk
Fix Committed on Branch:
10, trunk
Fixed in Maintenance Release:
Description
According to the documentation, the property name FastCompilation
has been misspelt as FastCompliation
.
- Status changed from New to Resolved
- Applies to branch 10, trunk added
- Fix Committed on Branch 10, trunk added
Fixed typo on both Saxon 10 and trunk branches.
- Status changed from Resolved to In Progress
Let's add some tests to see if the property actually has any effect...
I'll do this on the Java side.
Also, is it possible to retain the misspelt name as a deprecated synonym in 10.x (dropping it on trunk)?
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
.
- Status changed from In Progress to Resolved
This appears to have been resolved.
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 10.5 added
Bug fix applied to Saxon 10.5 maintenance release.
Please register to edit this issue
Also available in: Atom
PDF