From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Tom Ridge <tom.j.ridge+caml@googlemail.com>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] First release of P3: a combinator parser library, and parser generator
Date: Mon, 8 Apr 2013 12:03:39 +0100 [thread overview]
Message-ID: <48620B658D39465385431EB23E6876C8@erratique.ch> (raw)
In-Reply-To: <CABooLwO-_B7bHdadVM4QZyDcKAhf-RD=muBRm2kQCXmQ0KEGxQ@mail.gmail.com>
Hello Tom,
Combinator parsers were an obsession of mine a few years ago. I really liked the approach but eventually always ended up writing LL(k) parsers (xmlm, jsonm) by hand which so far has been the only "technology" that allows me to give the best error messages/correction, to handle asynchronous IO, and to remain reasonably efficient.
Could you maybe comment on these points:
* What's the error handling strategy ? Is there support for error correction ?
* Is there support for non-blocking parsing (asynchronous IO) ?
Best,
Daniel
next prev parent reply other threads:[~2013-04-08 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 10:28 Tom Ridge
2013-04-08 11:03 ` Daniel Bünzli [this message]
2013-04-08 11:33 ` Tom Ridge
2013-04-08 12:29 ` Daniel Bünzli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48620B658D39465385431EB23E6876C8@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@inria.fr \
--cc=tom.j.ridge+caml@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).