Project

Profile

Help

Bug #2743

closed

Line numbers of XQuery global variables are out by one

Added by Michael Kay almost 8 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Diagnostics
Sprint/Milestone:
Start date:
2016-05-12
Due date:
% Done:

100%

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

Description

The line number associated with an XQuery global variable declaration is out by one (if the variable is declared on line 4, the value of GlobalVariable.getLineNumber() is 5.) This affects some run-time diagnostics and tracing output.

Actions #1

Updated by Michael Kay almost 8 years ago

  • Category set to Diagnostics
  • Status changed from New to Resolved
  • Fix Committed on Branch 9.7, 9.8 added

Patch being committed on the 9.7 and 9.8 branches. A simple change to XQueryParser.parseVariableDeclaration(), which needs to add 1 to the line number obtained from the tokenizer, as tokenizer line numbers are zero-based.

Actions #2

Updated by O'Neil Delpratt almost 8 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in Maintenance Release 9.7.0.5 added

Bug fix applied in the Saxon 9.7.0.5 maintenance release.

Actions #3

Updated by O'Neil Delpratt almost 8 years ago

  • Sprint/Milestone set to 9.7.0.5
Actions #4

Updated by O'Neil Delpratt almost 7 years ago

  • Fix Committed on Branch trunk added
  • Fix Committed on Branch deleted (9.8)
Actions #5

Updated by O'Neil Delpratt almost 7 years ago

  • Applies to branch deleted (9.8)

Please register to edit this issue

Also available in: Atom PDF