Bug #4283
closed.NET API Documentation has two methods on XsltCompiler with the same signature Compile(Stream)
100%
Description
In the ,NET API documentation for XsltCompiler, there are two methods with the signature
public XsltExecutable Compile (Stream input)
that apparently do different things.
The second entry is a misnamed copy of the entry for CompilePackage(Stream input)
Updated by Michael Kay over 4 years ago
- Subject changed from .NET API Documentation has two methods on XsltCompiler with the same signature Compiler(Stream) to .NET API Documentation has two methods on XsltCompiler with the same signature Compile(Stream)
Updated by Debbie Lockett over 4 years ago
- Status changed from New to In Progress
The problem arises when there are method names which are a substring of another. Here XsltCompiler has a number of Compile
methods as well as CompilePackage
, CompilePackages
, and CompileAssociatedStylesheet
.
Patch required in merge.xsl stylesheet, in the match="method"
template, to improve the $apimember
select expression to handle this.
To catch other possible problems, add warning messages if $apimember
is empty (here, and similarly for the match templates for constructor
, property
, and field
. This reveals some other further issues to do with generic types, which meant that method comments were not being picked up (i.e. for EmptyEnumerator<T>
methods Dispose
, MoveNext
, Reset
; Feature<T>.byName
; and Predicate<T>.matches
). Further patches in merge.xsl added to resolve this (i.e. update the f:extract-params
function).
Committed updates to MyDotNet/doctools/merge.xsl stylesheet under build99 and build100.
Updated by Debbie Lockett over 4 years ago
- Status changed from In Progress to Resolved
- Applies to branch trunk added
- Fix Committed on Branch 9.9, trunk added
Online 9.9 .NET API documentation updated (XML and HTML versions) with fixes.
Updated by O'Neil Delpratt over 4 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 9.9.1.5 added
Bug fix applied in the Saxon 9.9.1.5 maintenance release.
Please register to edit this issue