caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Francois Pottier <Francois.Pottier@inria.fr>
To: caml-list@inria.fr
Subject: [Caml-list] New release of Menhir (20141215)
Date: Wed, 17 Dec 2014 21:14:48 +0100	[thread overview]
Message-ID: <20141217201448.GA27253@yquem.inria.fr> (raw)


Dear OCaml users,

I have recently started making a series of changes in Menhir, inspired by
the work of Frédéric Bour on Merlin (a smart emacs-mode for OCaml, which
uses a modified version of Menhir). Thanks to Frédéric for his stimulating
ideas, and thanks to Gabriel Scherer for not letting me sleep until I
promised I would do something about them! :-)

I have made a first release a couple days ago. The relevant chunk of the
CHANGES file is appended below. In summary, a new incremental API is
available; Menhir now requires ocaml 4.02; and a couple of obscure features
(--error-recovery and $previouserror) have been removed in the interest of
speed and simplicity.

The incremental API means that you can take a snapshot of the parser's state,
essentially at no cost, at any time. It also means that the parser no longer
drives the lexer; you drive the lexer, and you provide tokens to the parser
when it requests them. This can be convenient if the lexer is in a monad (the
Lwt monad, for instance).

More changes are planned. The type "env" exposed by the new incremental API is
currently opaque. We are planning to offer a range of functions that allow
inspecting and building values of type "env". This should allow the user to
implement new error handling and error recovery strategies outside of Menhir.

The new release is available now as a .tar.gz archive:

  http://gallium.inria.fr/~fpottier/menhir/menhir-20141215.tar.gz

It is also available via opam ("opam install menhir").

Cheers,

-- 
François Pottier
Francois.Pottier@inria.fr
http://gallium.inria.fr/~fpottier/

2014/12/15:
New incremental API (in --table mode only), inspired by Frédéric Bour.

2014/12/11:
Menhir now reports an error if one of the start symbols produces
either the empty language or the singleton language {epsilon}.

Although some people out there actually define a start symbol that recognizes
{epsilon} (and use it as a way of initializing or re-initializing some global
state), this is considered bad style. Furthermore, by ruling out this case, we
are able to simplify the table back-end a little bit.

2014/12/12:
A speed improvement in the code back-end.

2014/12/08:
Menhir now requires OCaml 4.02 (instead of 3.09).

2014/12/02:
Removed support for the $previouserror keyword.
Removed support for --error-recovery mode.

             reply	other threads:[~2014-12-17 20:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17 20:14 Francois Pottier [this message]
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
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=20141217201448.GA27253@yquem.inria.fr \
    --to=francois.pottier@inria.fr \
    --cc=caml-list@inria.fr \
    /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).