From: skaller <skaller@users.sourceforge.net>
To: dypgen@ml.free.fr
Cc: caml <caml-list@yquem.inria.fr>
Subject: Dypgen C++ grammar
Date: Sat, 23 Jun 2007 00:36:20 +1000 [thread overview]
Message-ID: <1182522980.6334.4.camel@rosella.wigram> (raw)
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
next reply other threads:[~2007-06-22 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 14:36 skaller [this message]
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
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=1182522980.6334.4.camel@rosella.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@yquem.inria.fr \
--cc=dypgen@ml.free.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).