Actions
Bug #5407
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)
XX compiler outputs its own location on an error
Start date:
2022-03-18
Due date:
% Done:
100%
Estimated time:
SEF Generated with:
Platforms:
Company:
-
Contact person:
-
Additional contact persons:
-
Description
When the XX compiler detects an error, typical output might be
Compiling stylesheet /Users/mike/GitHub/saxon-js-enterprise/src/test/testdriver/testdriverNodeJS.xsl
Failed to compile stylesheet: No binding for variable Q{}message-level
Error XPST0008 at static.xsl#1057
Failed to compile stylesheet:
Error XPST0008 at static.xsl#1057
No binding for variable Q{}message-level
Several problems here:
(a) there's no indication of where we are in the stylesheet being compiled
(b) We don't need to know the location in the compiler where the error was detected (static.xsl#1057)
(c) We certainly don't need to be told twice.
Note: the actual error was a static variable being referenced before the declaration.
Please register to edit this issue
Actions
Also available in: Atom PDF Tracking page