From: yoann padioleau <padator@wanadoo.fr>
To: Alex Baretta <alex@barettadeit.com>, Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Yacc limitations
Date: Thu, 22 Sep 2005 18:46:33 +0200 (CEST) [thread overview]
Message-ID: <27582143.1127407593127.JavaMail.www@wwinf1503> (raw)
> 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.
I personnaly use ocamlyacc and even if there is some difficulties, I like it.
The problems is when there is an ambiguity in the grammar, in which case I look at the output file
generated by ocamlyacc -v, C-s "conflict" in the file, and hope that my brain will find an easy solution.
All the ocaml project that I know that need some complex parsing use ocamlyacc.
Some people also use streams but are limited to write LL(1) grammars.
Some people use parser combinators to do the same kind of stuff that stream offers.
What is the problem with your SQL grammar and with ocamlyacc ?
next reply other threads:[~2005-09-22 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 16:46 yoann padioleau [this message]
2005-09-22 17:08 ` brogoff
-- strict thread matches above, loose matches on Subject: below --
2005-09-23 9:29 yoann padioleau
2005-09-23 12:51 ` Alex Baretta
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
2005-09-22 16:37 ` Christophe TROESTLER
2005-09-23 6:05 ` Jake A. Kirilenko
2005-09-23 15:30 ` Alan Falloon
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=27582143.1127407593127.JavaMail.www@wwinf1503 \
--to=padator@wanadoo.fr \
--cc=alex@barettadeit.com \
--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;
as well as URLs for NNTP newsgroup(s).