Bind parsers; reparse consumed data
I have a parser for a URI's query. The query is hex-/URI-encoded.
I also have a parser for the decoded string; one that yields the key-value-option pairs from the query params.
I'd like to do a two-phase pass; one to detect the query string, another to parse the contents of the query string; and combine these into a single FParsec parser.
Or in short;
let private Predicate i =
isPchar i
|| i = 0x2f // /
|| i = 0x3f // ?
let contentP =
PercentEncoding.makeParser Predicate
let paramsP =
contentP >>= fun q ->
run QueryParams.queryParamsP q
However, contentP advances the state of the CharStream, and run ... yields a ParseResult, not a parser. I'd really like to do something like contentP |> Parser.bindSuccess queryParamsP, while returning expected parser state.
How to express this with FParsec?
f# fparsec
asked Nov 16 '18 at 15:52
HenrikHenrik
6,81644172
add a comment |
I have a parser for a URI's query. The query is hex-/URI-encoded.
I also have a parser for the decoded string; one that yields the key-value-option pairs from the query params.
I'd like to do a two-phase pass; one to detect the query string, another to parse the contents of the query string; and combine these into a single FParsec parser.
Or in short;
let private Predicate i =
isPchar i
|| i = 0x2f // /
|| i = 0x3f // ?
let contentP =
PercentEncoding.makeParser Predicate
let paramsP =
contentP >>= fun q ->
run QueryParams.queryParamsP q
However, contentP advances the state of the CharStream, and run ... yields a ParseResult, not a parser. I'd really like to do something like contentP |> Parser.bindSuccess queryParamsP, while returning expected parser state.
How to express this with FParsec?
f# fparsec
asked Nov 16 '18 at 15:52
HenrikHenrik
6,81644172
You might be able to do something with thewithSkippedStringparser.
– rmunn
Nov 16 '18 at 18:27
add a comment |
I have a parser for a URI's query. The query is hex-/URI-encoded.
I also have a parser for the decoded string; one that yields the key-value-option pairs from the query params.
I'd like to do a two-phase pass; one to detect the query string, another to parse the contents of the query string; and combine these into a single FParsec parser.
Or in short;
let private Predicate i =
isPchar i
|| i = 0x2f // /
|| i = 0x3f // ?
let contentP =
PercentEncoding.makeParser Predicate
let paramsP =
contentP >>= fun q ->
run QueryParams.queryParamsP q
However, contentP advances the state of the CharStream, and run ... yields a ParseResult, not a parser. I'd really like to do something like contentP |> Parser.bindSuccess queryParamsP, while returning expected parser state.
How to express this with FParsec?
f# fparsec
asked Nov 16 '18 at 15:52
HenrikHenrik
6,81644172
I have a parser for a URI's query. The query is hex-/URI-encoded.
I also have a parser for the decoded string; one that yields the key-value-option pairs from the query params.
I'd like to do a two-phase pass; one to detect the query string, another to parse the contents of the query string; and combine these into a single FParsec parser.
Or in short;
let private Predicate i =
isPchar i
|| i = 0x2f // /
|| i = 0x3f // ?
let contentP =
PercentEncoding.makeParser Predicate
let paramsP =
contentP >>= fun q ->
run QueryParams.queryParamsP q
However, contentP advances the state of the CharStream, and run ... yields a ParseResult, not a parser. I'd really like to do something like contentP |> Parser.bindSuccess queryParamsP, while returning expected parser state.
How to express this with FParsec?
f# fparsec
f# fparsec
asked Nov 16 '18 at 15:52
HenrikHenrik
6,81644172
asked Nov 16 '18 at 15:52
HenrikHenrik
6,81644172
asked Nov 16 '18 at 15:52
HenrikHenrik
6,81644172
asked Nov 16 '18 at 15:52
HenrikHenrik
6,81644172
asked Nov 16 '18 at 15:52
HenrikHenrik
6,81644172
6,81644172
You might be able to do something with thewithSkippedStringparser.
– rmunn
Nov 16 '18 at 18:27
add a comment |
You might be able to do something with thewithSkippedStringparser.
– rmunn
Nov 16 '18 at 18:27
You might be able to do something with the
withSkippedString parser.– rmunn
Nov 16 '18 at 18:27
You might be able to do something with the
withSkippedString parser.– rmunn
Nov 16 '18 at 18:27
add a comment |
0
active
oldest
votes
Your Answer
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%2f53341284%2fbind-parsers-reparse-consumed-data%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%2f53341284%2fbind-parsers-reparse-consumed-data%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
You might be able to do something with the
withSkippedStringparser.– rmunn
Nov 16 '18 at 18:27