Project

Profile

Help

Bug #1942

closed

Function current should have been resolved at compile time

Added by Michael Kay almost 11 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
XSLT conformance
Sprint/Milestone:
-
Start date:
2013-12-02
Due date:
% Done:

100%

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

Description

The message in the subject line may be produced when a match pattern that is compiled as a GeneralPositionalPattern contains a call on current() within a predicate. The class GeneralPositionalPredicate is used for a particular class of patterns whose result is sensitive, or potentially sensitive, to the position of a node relative to other nodes. In the particular case in question however GeneralPositionalPredicate was used when there was no position-sensitivity - see the reopening of bug 1908. A patch to GeneralPositionalPattern is being committed that causes calls on current() to be properly resolved.


Related issues

Related to Saxon - Bug #1908: Performance: patterns calling a function in a predicateClosedMichael Kay2013-09-20

Actions
Related to Saxon - Bug #1933: NullPointerException when current() used in a pattern predicateClosed2013-11-06

Actions
Actions #1

Updated by Michael Kay almost 11 years ago

  • Status changed from New to Resolved
Actions #2

Updated by O'Neil Delpratt almost 11 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in version set to 9.5.1.4

Bug fix applied in Saxon maintenance release 9.5.1.4

Please register to edit this issue

Also available in: Atom PDF