Actions
Bug #6485
closed![Author: Michael Kay](https://www.gravatar.com/avatar/db6526d63053f09b62e52c2da8b2230a?rating=PG&size=50&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
![Assignee: Michael Kay](https://www.gravatar.com/avatar/db6526d63053f09b62e52c2da8b2230a?rating=PG&size=22&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
Undeclared variable in XQuery - poor diagnostics
Start date:
2024-07-19
Due date:
% Done:
0%
Estimated time:
Legacy ID:
Applies to branch:
trunk
Fix Committed on Branch:
trunk
Fixed in Maintenance Release:
Platforms:
.NET, Java
Description
If a query contains a reference to an undeclared variable, we assume initially it is a forward reference to a global variable declared later. If it is still outstanding at the end of the module, we report an error that the variable is undeclared, but we have no location information for where the variable reference appeared. Example attached.
Files
Please register to edit this issue
Actions