From: Joel Reymont <joelr1@gmail.com>
To: "Markus Mottl" <markus.mottl@gmail.com>
Cc: Francois.Pottier@inria.fr, "Caml List" <caml-list@inria.fr>
Subject: Re: [Caml-list] Size of produced parser: menhir vs ocamlyacc
Date: Fri, 30 Mar 2007 14:51:00 +0100 [thread overview]
Message-ID: <CF22987A-5CA8-4229-9C7F-BC522F03A25C@gmail.com> (raw)
In-Reply-To: <f8560b80703300645y1a73ec7ct1dabd5e8bb2408db@mail.gmail.com>
On Mar 30, 2007, at 2:45 PM, Markus Mottl wrote:
> I also haven't done any serious benchmarks, but I remember seeing
> menhir beat ocamlyacc on some of my parsers.
How complex were they?
--
http://wagerlabs.com/
next prev parent reply other threads:[~2007-03-30 13:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 13:14 Joel Reymont
2007-03-30 13:31 ` [Caml-list] " Francois Pottier
2007-03-30 13:45 ` Markus Mottl
2007-03-30 13:51 ` Joel Reymont [this message]
2007-03-30 14:26 ` Markus Mottl
2007-03-30 14:28 ` Joel Reymont
2007-03-30 15:58 ` skaller
2007-04-01 0:42 ` Markus Mottl
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=CF22987A-5CA8-4229-9C7F-BC522F03A25C@gmail.com \
--to=joelr1@gmail.com \
--cc=Francois.Pottier@inria.fr \
--cc=caml-list@inria.fr \
--cc=markus.mottl@gmail.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).