From: Taras Glek <tglek@shaw.ca>
To: skaller <skaller@users.sourceforge.net>
Cc: dypgen@ml.free.fr, caml <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Dypgen C++ grammar
Date: Mon, 25 Jun 2007 14:26:29 -0700 [thread overview]
Message-ID: <46803305.1000309@shaw.ca> (raw)
In-Reply-To: <1182522980.6334.4.camel@rosella.wigram>
Hi Scott,
Why write yet another incomplete C++ parser? You can already get a very
nice OCaml representation of a C++ program through olmar(
http://www.cs.ru.nl/~tews/olmar/ ).
If that doesn't suit your needs, why not point out the problems and
maybe work together to solve them? Parsing C++ is hard enough that there
isn't a single complete open source C++ parser other than g++.
Olmar/elsa represent the second best C++ parser and everybody else isn't
even close. Unlike g++, elsa is designed to support more than just
compilers (ie has a much nicer API) and has a more liberal license.
My understanding is that there are Cil people interested in making elsa
work better with OCaml.
If the above doesn't suit you, your best bet would be to convert the
elsa grammar into OCaml (elkhound already has some ml support), but that
will mean redoing a serious amount of type resolution work.
Taras
skaller wrote:
> Is anyone interested in developing a C++ parser, possibly using
> FrontC and/or CIL as the starting point, but using Dypgen
> as the parser engine?
>
> I have made some modification to FrontC/Cil to support
> some C++ constructions, but Ocamlyacc (LALR1) just can't cope
> with C++.
>
> OTOH, Scott McPeak has a C++ grammar for Elkhound which is
> a C++ based GLR engine, with BSD licence, so it may be possible
> to adapt that.
>
>
next prev parent reply other threads:[~2007-06-25 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 14:36 skaller
2007-06-22 17:33 ` [Caml-list] " Christopher L Conway
2007-06-22 19:29 ` David Hall
2007-06-23 10:11 ` Lukasz Dobrek
2007-06-25 21:26 ` Taras Glek [this message]
2007-06-26 6:38 ` skaller
2007-06-26 6:45 ` Jon Harrop
2007-06-26 20:11 ` Taras Glek
2007-06-27 13:48 ` Jon Harrop
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=46803305.1000309@shaw.ca \
--to=tglek@shaw.ca \
--cc=caml-list@yquem.inria.fr \
--cc=dypgen@ml.free.fr \
--cc=skaller@users.sourceforge.net \
/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