caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "David Hall" <dlwh@stanford.edu>
To: "Christopher L Conway" <cconway@cs.nyu.edu>
Cc: skaller <skaller@users.sourceforge.net>,
	dypgen@ml.free.fr, caml <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Dypgen C++ grammar
Date: Fri, 22 Jun 2007 12:29:37 -0700	[thread overview]
Message-ID: <5efa98b30706221229m70513c68n5a36bc7395fa07a7@mail.gmail.com> (raw)
In-Reply-To: <4a051d930706221033l55f89460k1695c3dc88c3fd12@mail.gmail.com>

On 6/22/07, Christopher L Conway <cconway@cs.nyu.edu> wrote:
> 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)
>

It's sort of already been done with GCC-XML:

"The purpose of the GCC-XML extension is to generate an XML
description of a C++ program from GCC's internal representation. Since
XML is easy to parse, other development tools will be able to work
with C++ programs without the burden of a complicated C++ parser."

http://www.gccxml.org/HTML/Index.html

-- David Hall

>
> 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
> >
> >
>
> _______________________________________________
> 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
>


  reply	other threads:[~2007-06-22 19:29 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 [this message]
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=5efa98b30706221229m70513c68n5a36bc7395fa07a7@mail.gmail.com \
    --to=dlwh@stanford.edu \
    --cc=caml-list@yquem.inria.fr \
    --cc=cconway@cs.nyu.edu \
    --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;
as well as URLs for NNTP newsgroup(s).