Bug #4283: .NET API Documentation has two methods on XsltCompiler with the same signature Compile(Stream) - Saxon - Saxonica Developer Community

Actions

Send by e-mail Copy link

Bug #4283

closed

.NET API Documentation has two methods on XsltCompiler with the same signature Compile(Stream)

Added by Michael Kay over 4 years ago. Updated over 4 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Debbie Lockett

Category:

Documentation

Sprint/Milestone:

Start date:

2019-08-15

Due date:

% Done:

100%

Estimated time:

Legacy ID:

Applies to branch:

9.9, trunk

Fix Committed on Branch:

9.9, trunk

Fixed in Maintenance Release:

9.9.1.5

Platforms:

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)

Actions

Copy link

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)

Actions

Copy link

Updated by Michael Kay over 4 years ago

Description updated (diff)

Actions

Copy link

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).