Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Hendrik Tews <tews@cs.ru.nl>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Looking for full-fledged C++ Parser with OCAML interface
Date: Mon, 31 Mar 2008 11:51:07 +0200	[thread overview]
Message-ID: <wwusky7xlv8.fsf@tandem.cs.ru.nl> (raw)
In-Reply-To: <47D0F155.4080909@ropas.snu.ac.kr> (Soonho Kong's message of "Fri, 07 Mar 2008 16:40:05 +0900")

Hi,

Soonho Kong <soon@ropas.snu.ac.kr> writes:

   Olmar(http://www.cs.ru.nl/~tews/olmar/) was the best candidate among
   them. I have two questions about it.

If you try Olmar I would be interested in your experience!
Further, as the documentation is inexistent (there are almost no
Olmar users), if you hit a problem, don't hesitate to ask me. 

For documenting the Olmar ast see the Elsa ast nodes pages in the
Mozilla wiki (http://wiki.mozilla.org/Elsa_ast_nodes). There is
not much additional information in there, but at least you can
click through the interfaces and add your own findings. We know a
bit more than what's in the wiki, so don't hesitate to ask on the
oink-devel mailing list.

If you try Olmar I would suggest that you use the cvs version,
there have been lots of changes/improvements since the last
release. 

    2. If anyone have used Olmar before, I'd like to listen to your
   experience with it. I'm curious of its tolerance with various C++
   dialects, robustness, and efficiency on the code used in real world.

Olmar relies on Elsa for parsing, so this is really a question
about the capabilities of Elsa. The current Elsa version can't
parse all new gcc headers, through I never run into this problem
and use whatever header are installed on my system. For Mozilla
this was a real problem, but Taras Glek's blog seems to indicate
that they fixed most of those in their Elsa branch in the pork
repository. A problem with Elsa is that the current maintainer
makes it really difficult to contribute something back. Therefore
everybody has there own (incompatible) Elsa branch. A problem
with Olmar is that you cannot simply use it with a different Elsa
branch. But I am working in that direction...

However, my current contract ends this April and I might not have
any time left for Olmar then. If you decide for Olmar you must be
prepared to take over maintenance. 


David Teller <David.Teller@univ-orleans.fr> writes:

   I personally haven't used it, but I'm pretty sure it's what Mozilla is
   using to rewrite their code for automatic exception rewriting. Which is
   a good sign.

I am not completely sure, but I would be surprised, if Mozilla
already uses Olmar. 



Sorry for the late reply, but I sometimes get overwhelmed by the
traffic on the ocaml-list and then I am suddenly 500 messages
behind... 

Bye,

Hendrik Tews


      parent reply	other threads:[~2008-03-31  9:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07  7:40 Soonho Kong
2008-03-07  8:00 ` [Caml-list] " David Teller
2008-03-07 13:54 ` Christopher L Conway
2008-03-07 14:28   ` Gordon Henriksen
2008-03-31  9:51 ` Hendrik Tews [this message]

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=wwusky7xlv8.fsf@tandem.cs.ru.nl \
    --to=tews@cs.ru.nl \
    --cc=caml-list@yquem.inria.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