From: Pierre Boulet <Pierre.Boulet@lifl.fr>
To: Christophe Raffalli <christophe.raffalli@univ-savoie.fr>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Yacc limitations
Date: Mon, 26 Sep 2005 13:54:06 +0200 [thread overview]
Message-ID: <4337E15E.5000307@lifl.fr> (raw)
In-Reply-To: <4332AD1B.1060704@univ-savoie.fr>
Hi,
I like using Camlp4 for that purpose. It has a very convenient way to
write parsers (the EXTEND notation). Its power is not directly
comparable to LALR but I find it suiting my needs (at least it is enough
to parse ocaml). The main pain is writing the lexer that feeds the
parser. That I remember from the early days of camlp4, it may have changed.
Regards,
Pierre.
Christophe Raffalli a écrit :
> Alex Baretta a écrit :
>
>> I am getting very much annoyed with the obtusity of the LALR-yacc parser
>> generators. I have unsurmountable difficulties at teaching ocamlyacc how
>> to parse SQL decently.
>>
>> What is the "way to go" in terms of parser generators for Ocaml? I'd
>> like to see if there is some level of agreement in the community on this
>> issue.
>>
>
> may be give a try to elkhound
> (http://www.cs.berkeley.edu/~smcpeak/elkhound/) ? It generated both
> OCaml and C++. I haven't used it, But it seems nice and will remove the
> LALR(1) constraint .
>
>
>> Alex
>>
>>
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
next prev parent reply other threads:[~2005-09-26 11:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 9:57 Alex Baretta
2005-09-22 13:09 ` [Caml-list] " Christophe Raffalli
2005-09-26 11:54 ` Pierre Boulet [this message]
[not found] ` <4332ACF2.6020702@univ-savoie.fr>
2005-09-22 14:05 ` Alex Baretta
2005-09-22 16:37 ` Christophe TROESTLER
2005-09-23 6:05 ` Jake A. Kirilenko
2005-09-23 15:30 ` Alan Falloon
2005-09-22 16:46 yoann padioleau
2005-09-22 17:08 ` brogoff
2005-09-23 9:29 yoann padioleau
2005-09-23 12:51 ` Alex Baretta
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=4337E15E.5000307@lifl.fr \
--to=pierre.boulet@lifl.fr \
--cc=caml-list@inria.fr \
--cc=christophe.raffalli@univ-savoie.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).