Project

Profile

Help

Actions
Send by e-mail Copy link

Bug #6379

closed

Default implementation of fn:deep-equal

Added by Norm Tovey-Walsh about 1 month ago. Updated 1 day ago.

Status:
Resolved
Priority:
Low
Assignee:
Michael Kay
Category:
Internals
Sprint/Milestone:
-
Start date:
2024-03-27
Due date:
% Done:

0%

Estimated time:
Legacy ID:
Applies to branch:
12, trunk
Fix Committed on Branch:
12, trunk
Fixed in Maintenance Release:
Platforms:
.NET, Java

Description

I happened to trace my way through a call to deep equal in Saxon HE 12.4 and I was a little bit surprised to find that it's using the DeepEqual40 implementation. I wonder if that was intentional...

Actions
Copy link
 #1

Updated by Michael Kay 2 days ago

All the 3.1 tests pass when we use DeepEqual40, and they don't pass if I revert back to the DeepEqual code. I think the old DeepEqual is now retained only to support the saxon:deep-equal extension function, so some appropriate renaming of classes is needed to reflect this.

Actions
Copy link
 #2

Updated by Michael Kay 1 day ago

  • Applies to branch 12, trunk added
  • Fix Committed on Branch 12, trunk added
  • Platforms .NET, Java added

All XPath versions now use the DeepEqual40 code, which is renamed DeepEqual.

The old DeepEqual code is renamed SaxonDeepEqual, and is now used for the Saxon extension function, and for some internal purposes such as test result assertions.

Actions
Copy link
 #3

Updated by Michael Kay 1 day ago

  • Category set to Internals
  • Status changed from New to Resolved
  • Assignee set to Michael Kay

Please register to edit this issue

Actions
Send by e-mail Copy link

Also available in: Atom PDF