From: "Christopher L Conway" <cconway@cs.nyu.edu>
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: Fri, 22 Jun 2007 13:33:20 -0400 [thread overview]
Message-ID: <4a051d930706221033l55f89460k1695c3dc88c3fd12@mail.gmail.com> (raw)
In-Reply-To: <1182522980.6334.4.camel@rosella.wigram>
I would be extremely interested in a C++ parser for OCaml, especially
if it was largely compatible with CIL. The conventional wisdom is that
this is a lost cause, it's just too much work. E.g., in order to
handle real code, you'd need to support almost 30 years' worth of
language variants and historical compiler bugs that have become de
facto "features", etc.
Another approach would be to modify GCC so that it's intermediate
representation can be fed to outside tools. As a bonus, this would
provide support for Java, Fortran, and all the other languages
front-endsd in the GCC suite. Unfortunately, unless the GCC
maintainers have changed their position, this would require forking
the front end, though I suspect the changes required to implement this
are fairly minor. (See, e.g., this old discussion from the GCC list:
http://gcc.gnu.org/ml/gcc/2000-10/msg00103.html)
Chris
On 6/22/07, skaller <skaller@users.sourceforge.net> 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.
>
> --
> John Skaller <skaller at users dot sf dot net>
> Felix, successor to C++: http://felix.sf.net
>
> _______________________________________________
> 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:[~2007-06-22 17:33 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 ` Christopher L Conway [this message]
2007-06-22 19:29 ` [Caml-list] " David Hall
2007-06-23 10:11 ` Lukasz Dobrek
2007-06-25 21:26 ` Taras Glek
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=4a051d930706221033l55f89460k1695c3dc88c3fd12@mail.gmail.com \
--to=cconway@cs.nyu.edu \
--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