From: Francois Pottier <Francois.Pottier@inria.fr>
To: Caml Mailing List <caml-list@yquem.inria.fr>
Subject: [ANNOUNCE] Alpha release of Menhir, an LR(1) parser generator for ocaml
Date: Mon, 12 Dec 2005 18:58:38 +0100 [thread overview]
Message-ID: <20051212175838.GA8502@yquem.inria.fr> (raw)
Dear Caml users,
We are proud to announce the first release of Menhir. Menhir compiles LR(1)
grammar specifications to OCaml code.
Menhir is 90% compatible with ocamlyacc. That is, existing ocamlyacc grammar
specifications are accepted and compiled by Menhir; the resulting parsers run
and produce correct parse trees, except they produce incorrect position
information, because none of the functionality of module Parsing is
supported. Porting a grammar specification from ocamlyacc to Menhir requires
replacing all calls to the Parsing module with new keywords.
Why switch from ocamlyacc to Menhir? In short,
* Menhir offers parameterized nonterminal symbols as well as a library of
standard definitions, including options, sequences, and lists. It also
offers limited support for EBNF syntax.
* ocamlyacc accepts LALR(1) grammars; Menhir accepts LR(1) grammars, thus
avoiding certain artificial conflicts.
* Menhir explains conflicts in terms of the grammar, not (only) in terms of
the automaton.
* Menhir allows grammar specifications to be split over multiple files. It
also allows several grammars to share a single set of tokens.
* Menhir produces reentrant parsers.
* Menhir is able to produce parsers that are parameterized by Ocaml modules.
* ocamlyacc requires semantic values to be referred to via keywords: $1, $2,
and so on. Menhir allows semantic values to be explicitly named.
* Menhir's error and warning messages are usually more numerous and better
than ocamlyacc's.
A more detailed comparison between ocamlyacc and Menhir appears in Menhir's
documentation.
This is an ALPHA-quality release, so there certainly remain a lot of bugs
to iron out. Nevertheless, we encourage intrepid testers to have a look
and send suggestions and bug reports our way. Thanks for your attention!
Menhir requires ocaml 3.09. The source distribution and the documentation can
be found at
http://pauillac.inria.fr/~fpottier/menhir/menhir-20051212.tar.gz
http://pauillac.inria.fr/~fpottier/menhir/manual.pdf
--
François Pottier and Yann Régis-Gianas
{Francois.Pottier,Yann.Regis-Gianas}@inria.fr
http://pauillac.inria.fr/~fpottier/
http://pauillac.inria.fr/~regisgia/
next reply other threads:[~2005-12-12 17:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 17:58 Francois Pottier [this message]
2005-12-12 19:51 ` [Caml-list] " "Márk S. Zoltán"
2005-12-13 21:07 ` Nathaniel Gray
2005-12-14 6:08 ` skaller
2005-12-14 9:04 ` Francois Pottier
2005-12-14 10:27 ` Alessandro Baretta
2005-12-14 21:04 ` skaller
2005-12-15 8:46 ` Francois Pottier
2005-12-15 11:03 ` skaller
2005-12-14 20:51 ` skaller
2005-12-14 22:15 ` Joaquin Cuenca Abela
2005-12-15 8:40 ` Francois Pottier
2005-12-15 6:35 ` Stefan Monnier
2005-12-15 8:47 ` [Caml-list] " Francois Pottier
2005-12-15 16:41 ` Stefan Monnier
2005-12-15 16:50 ` Francois Pottier
2005-12-15 18:56 ` Stefan Monnier
2005-12-30 21:57 ` Florian Weimer
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=20051212175838.GA8502@yquem.inria.fr \
--to=francois.pottier@inria.fr \
--cc=caml-list@yquem.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