caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: Taras Glek <tglek@shaw.ca>
Cc: dypgen@ml.free.fr, caml <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Dypgen C++ grammar
Date: Tue, 26 Jun 2007 16:38:44 +1000	[thread overview]
Message-ID: <1182839924.13033.93.camel@rosella.wigram> (raw)
In-Reply-To: <46803305.1000309@shaw.ca>

On Mon, 2007-06-25 at 14:26 -0700, Taras Glek wrote:
> 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/ ).

Because last I looked, olmar doesn't work, and that's
because Elkhound and Elsa, on which they're based, don't work.
By that I mean, there are bugs. 

> If that doesn't suit your needs, why not point out the problems and 
> maybe work together to solve them? 

Elkhound and Elsa are both C++ programs, which creates 
portability issues, and the team maintaining them refused 
to cooperate with my requirements.

My system Felix consists of an Ocaml based compiler,
which generates C++ sources.

I actually have a *fork* of Elkhound built in to the
compile and run time system for generating parsers,
but this doesn't apply to parsing Felix sources:
I'm currently switching from Ocamlyacc to Dypgen as a
parser.

Frankly .. I want an embeddable Ocaml code: binding
to a C++ built executable is tricky (you'd need to
use some crud like XML as an interchange format),
and it isn't extensible.

Using Frontc/Cil, which is *also* part of Felix,
is much better -- I have already embedded part of
the C parsing capabilities directly into the Felix compiler.

The bottom line is that I want code written in Ocaml
because I'm sooooo sick of portability hassles.. :)

-- 
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net


  reply	other threads:[~2007-06-26  6:38 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
2007-06-26  6:38   ` skaller [this message]
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=1182839924.13033.93.camel@rosella.wigram \
    --to=skaller@users.sourceforge.net \
    --cc=caml-list@yquem.inria.fr \
    --cc=dypgen@ml.free.fr \
    --cc=tglek@shaw.ca \
    /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).