how to get context of expectation failures in boost spirit qi?
I am using boost spirit v1.67.
I want the parser to provide exact error codes, ie, contextual error messages as to where it failed.
For eg -
- InvalidNumber - Number greater than 2,147,483,647 for int_
- InvalidSequence - invalid sequence of characters AB, expecting BA.
Options I think would work, but would need advise on how to go about it-
- throw custom exceptions from on_error, and catch them after the parse method
- use on_error to track the exact failure and then save the error code in some variable which will be accessible later.
- accept a bit of invalid data in the parser only to flag it after the parser runs in post processing checks. (eg - accept long int instead of int and flag as an error in post processing if number is greater than max_int).
c++ boost boost-spirit boost-spirit-qi
add a comment |
I am using boost spirit v1.67.
I want the parser to provide exact error codes, ie, contextual error messages as to where it failed.
For eg -
- InvalidNumber - Number greater than 2,147,483,647 for int_
- InvalidSequence - invalid sequence of characters AB, expecting BA.
Options I think would work, but would need advise on how to go about it-
- throw custom exceptions from on_error, and catch them after the parse method
- use on_error to track the exact failure and then save the error code in some variable which will be accessible later.
- accept a bit of invalid data in the parser only to flag it after the parser runs in post processing checks. (eg - accept long int instead of int and flag as an error in post processing if number is greater than max_int).
c++ boost boost-spirit boost-spirit-qi
All these approaches are valid. There are examples of eacht of them on this site. I don't see what I can/should ask since the question is so broad (in the functional programming spirit you might prefer to represent an error node in the ast so you can adapt behaviour depending on surrounding context, or supply logic on partially parsed input)
– sehe
Jan 3 at 21:04
add a comment |
I am using boost spirit v1.67.
I want the parser to provide exact error codes, ie, contextual error messages as to where it failed.
For eg -
- InvalidNumber - Number greater than 2,147,483,647 for int_
- InvalidSequence - invalid sequence of characters AB, expecting BA.
Options I think would work, but would need advise on how to go about it-
- throw custom exceptions from on_error, and catch them after the parse method
- use on_error to track the exact failure and then save the error code in some variable which will be accessible later.
- accept a bit of invalid data in the parser only to flag it after the parser runs in post processing checks. (eg - accept long int instead of int and flag as an error in post processing if number is greater than max_int).
c++ boost boost-spirit boost-spirit-qi
I am using boost spirit v1.67.
I want the parser to provide exact error codes, ie, contextual error messages as to where it failed.
For eg -
- InvalidNumber - Number greater than 2,147,483,647 for int_
- InvalidSequence - invalid sequence of characters AB, expecting BA.
Options I think would work, but would need advise on how to go about it-
- throw custom exceptions from on_error, and catch them after the parse method
- use on_error to track the exact failure and then save the error code in some variable which will be accessible later.
- accept a bit of invalid data in the parser only to flag it after the parser runs in post processing checks. (eg - accept long int instead of int and flag as an error in post processing if number is greater than max_int).
c++ boost boost-spirit boost-spirit-qi
c++ boost boost-spirit boost-spirit-qi
asked Jan 3 at 16:01
vinzee93vinzee93
164
164
All these approaches are valid. There are examples of eacht of them on this site. I don't see what I can/should ask since the question is so broad (in the functional programming spirit you might prefer to represent an error node in the ast so you can adapt behaviour depending on surrounding context, or supply logic on partially parsed input)
– sehe
Jan 3 at 21:04
add a comment |
All these approaches are valid. There are examples of eacht of them on this site. I don't see what I can/should ask since the question is so broad (in the functional programming spirit you might prefer to represent an error node in the ast so you can adapt behaviour depending on surrounding context, or supply logic on partially parsed input)
– sehe
Jan 3 at 21:04
All these approaches are valid. There are examples of eacht of them on this site. I don't see what I can/should ask since the question is so broad (in the functional programming spirit you might prefer to represent an error node in the ast so you can adapt behaviour depending on surrounding context, or supply logic on partially parsed input)
– sehe
Jan 3 at 21:04
All these approaches are valid. There are examples of eacht of them on this site. I don't see what I can/should ask since the question is so broad (in the functional programming spirit you might prefer to represent an error node in the ast so you can adapt behaviour depending on surrounding context, or supply logic on partially parsed input)
– sehe
Jan 3 at 21:04
add a comment |
0
active
oldest
votes
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54025825%2fhow-to-get-context-of-expectation-failures-in-boost-spirit-qi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54025825%2fhow-to-get-context-of-expectation-failures-in-boost-spirit-qi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
All these approaches are valid. There are examples of eacht of them on this site. I don't see what I can/should ask since the question is so broad (in the functional programming spirit you might prefer to represent an error node in the ast so you can adapt behaviour depending on surrounding context, or supply logic on partially parsed input)
– sehe
Jan 3 at 21:04