Project

Profile

Help

Actions
Send by e-mail Copy link

Bug #5710

closed

Saxon .NET 10 : format supplied to XPathCompiler.SetDecimalFormatProperty must not be null

Added by Michael Kay about 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Low
Assignee:
Michael Kay
Category:
-
Sprint/Milestone:
-
Start date:
2022-10-05
Due date:
% Done:

0%

Estimated time:
Legacy ID:
Applies to branch:
Fix Committed on Branch:
10
Fixed in Maintenance Release:
10.9
Platforms:
.NET

Description

The API documentation for XPathCompiler.SetDecimalFormatProperty in Saxon.10 on .NET says that the format argument can be null, but this causes a null reference exception.

Actions
Copy link
 #1

Updated by Michael Kay about 2 years ago

The underlying Java code does not allow a null to be supplied.

So we must (a) change the ,NET API documentation, (b) check for null, (c), change the test driver so it doesn't try calling the method with a null argument.

Actions
Copy link
 #2

Updated by Michael Kay about 2 years ago

I've now changed it so the test driver doesn't call this method if the decimal format is unnamed. The consequence is that the relevant format-number tests are failing under XPath. They work in SaxonJ, and I'm having difficulty understanding why.

Actions
Copy link
 #3

Updated by O'Neil Delpratt almost 2 years ago

  • Fix Committed on Branch 10 added

For the Saxon 10 release I have modified XPathCompiler.SetDecimalFormatProperty to check for null. If the format argument is null throw a StaticError exception.

Actions
Copy link
 #4

Updated by Michael Kay over 1 year ago

  • Status changed from New to Closed
  • Fixed in Maintenance Release 10.9 added
  • Platforms .NET added

I'm assuming this was fixed in 10.9, and that we failed to update the issue to say so.

Please register to edit this issue

Actions
Send by e-mail Copy link

Also available in: Atom PDF