From: Christophe Raffalli <christophe.raffalli@univ-savoie.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Jane St Capital Ocaml Summer Project code?
Date: Sat, 15 Nov 2008 07:45:31 +0100 [thread overview]
Message-ID: <491E700B.2040705@univ-savoie.fr> (raw)
In-Reply-To: <20081115083050.4c2929a9.mle+ocaml@mega-nerd.com>
Erik de Castro Lopo a écrit :
> Christophe Raffalli wrote:
>
>
>> Have you looked at dypgen ... (http://dypgen.free.fr/), it even offers
>> integrated lexer in the latest version
>>
>
> I haven't really looked at that. What are the relative strengths and
> weaknesses of the two?
>
> Erik
>
Here is what I mostly like (you have a comparison table here
http://www.lama.univ-savoie.fr/~raffalli/ocaml-parsing.html:
dypgen :
- GLR instead of LR(1) : this gives much more elegant description of the
grammar (and the possibiliy of ambigous grammar) and there
is never a conflict. These are replaced by multiple parse trees (you can
choose a merge function that will report that as an error, if you think
your grammar should not be ambiguous).
- pattern matching in rule. Example: you define a grammar for list of
expressions of any-size, but you can restrict the usage
to list of length at least 1, 2, ... by pattern matching)
- late reject of a rule by raising an exception.
- self extensible lexer and parser with delimited scope.
menhir :
- should be faster because it is only LR(1), but I did not test
- you know for sure that your grammer is not ambiguous ...
prev parent reply other threads:[~2008-11-15 6:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 0:58 Erik de Castro Lopo
2008-11-12 1:52 ` [Caml-list] " Yaron Minsky
2008-11-12 8:17 ` Sylvain Le Gall
2008-11-12 23:03 ` [Caml-list] " Erik de Castro Lopo
2008-11-13 0:28 ` Yaron Minsky
2008-11-13 0:33 ` Erik de Castro Lopo
2008-11-13 22:13 ` Christophe Raffalli
2008-11-13 22:17 ` Christophe Raffalli
2008-11-14 21:30 ` Erik de Castro Lopo
2008-11-15 6:45 ` Christophe Raffalli [this message]
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=491E700B.2040705@univ-savoie.fr \
--to=christophe.raffalli@univ-savoie.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