From: Alex Baretta <alex@barettadeit.com>
To: Christophe Raffalli <christophe.raffalli@univ-savoie.fr>,
Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Yacc limitations
Date: Thu, 22 Sep 2005 16:05:29 +0200 [thread overview]
Message-ID: <4332BA29.1010304@barettadeit.com> (raw)
In-Reply-To: <4332ACF2.6020702@univ-savoie.fr>
Christophe Raffalli wrote:
> 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 .
Elkhound is C++ stuff. I really would prefer to avoid having to
introduce C++ in my toolchain. Is it possible to install Elkhound as a
Debian package and forget about it?
Alex
--
*********************************************************************
http://www.barettadeit.com/
Baretta DE&IT
A division of Baretta SRL
tel. +39 02 370 111 55
fax. +39 02 370 111 54
Our technology:
The Application System/Xcaml (AS/Xcaml)
<http://www.asxcaml.org/>
The FreerP Project
<http://www.freerp.org/>
next prev parent reply other threads:[~2005-09-22 14:08 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
[not found] ` <4332ACF2.6020702@univ-savoie.fr>
2005-09-22 14:05 ` Alex Baretta [this message]
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=4332BA29.1010304@barettadeit.com \
--to=alex@barettadeit.com \
--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).