From: Francois Pottier <Francois.Pottier@inria.fr>
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: Nicolas Ojeda Bar <no263@dpmms.cam.ac.uk>, caml-list@inria.fr
Subject: Re: [Caml-list] New release of Menhir (20141215)
Date: Thu, 18 Dec 2014 18:25:58 +0100 [thread overview]
Message-ID: <20141218172558.GA20049@yquem.inria.fr> (raw)
In-Reply-To: <1418916329.21394.62.camel@thinkpad.lan.sumadev.de>
On Thu, Dec 18, 2014 at 04:25:29PM +0100, Gerd Stolpmann wrote:
> followed by a BLOB or completely invalid. I haven't checked yet: could
> we inspect Menhir's state and see whether the only possible
> interpretation is a BLOB prefix? I.e. whether it is in the middle of a
> production
At this moment, it is not possible to inspect Menhir's state. In the future,
we are planning to allow it. However, I don't know if it would help with this
issue.
An idea that comes to mind is: Menhir's new incremental interface actually
allows you to fork the parser. When you find {342} in the input stream, you
could try two alternatives (viewing it as a blob token, and not viewing it as
a non-blob token) in parallel. If you can be certain that one of the two
alternatives will quickly die, then this approach might be tenable. It is
actually a form of poor man's GLR.
--
François Pottier
Francois.Pottier@inria.fr
http://gallium.inria.fr/~fpottier/
next prev parent reply other threads:[~2014-12-18 17:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 20:14 Francois Pottier
2014-12-18 12:45 ` Gerd Stolpmann
2014-12-18 14:19 ` Nicolas Ojeda Bar
2014-12-18 15:20 ` Daniel Bünzli
2014-12-18 15:34 ` Simon Cruanes
2014-12-18 16:02 ` Nicolas Ojeda Bar
2014-12-18 15:25 ` Gerd Stolpmann
2014-12-18 17:25 ` Francois Pottier [this message]
2014-12-22 11:13 ` oleg
2014-12-22 18:40 ` Dario Teixeira
2014-12-24 23:30 ` Francois Pottier
2014-12-26 11:13 ` Dario Teixeira
2014-12-26 11:31 ` Frédéric Bour
2014-12-26 12:16 ` Dario Teixeira
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=20141218172558.GA20049@yquem.inria.fr \
--to=francois.pottier@inria.fr \
--cc=caml-list@inria.fr \
--cc=info@gerd-stolpmann.de \
--cc=no263@dpmms.cam.ac.uk \
/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).