Use XQuery 3 syntax for private methods and try/catch #48
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@robwhitby Any update? |
|
I just checked it out and got errors running against MarkLogic 8.0-6. Also I have concerns that MarkLogic is a bit weird about how it handles errors, seem to remember the name and code getting switched or something stupid like that. So I can't merge this as is - if you want to fix the issues and test against MarkLogic 8 and 9 then I assure you it won't be left pending for another 3 years ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My motivation for this is to be able to parse the XRay code base using an XQuery parser generated by the REx parser generator. I am looking to examine and generate some stats about XQuery projects and XRay is one of the projects I am looking at.
These changes should all be compatible with
1.0-ml. I am not certain how MarkLogic populates the$err:variables in a catch statement, so my assumptions where I have changed try/catch may need a quick check...