From: David Teller <David.Teller@univ-orleans.fr>
To: Soonho Kong <soon@ropas.snu.ac.kr>
Cc: caml-list@yquem.inria.fr, Kwangkeun Yi <kwang@ropas.snu.ac.kr>,
grad@ropas.snu.ac.kr
Subject: Re: [Caml-list] Looking for full-fledged C++ Parser with OCAML interface
Date: Fri, 07 Mar 2008 09:00:56 +0100 [thread overview]
Message-ID: <1204876856.6577.1.camel@Blefuscu> (raw)
In-Reply-To: <47D0F155.4080909@ropas.snu.ac.kr>
Hi,
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.
Cheers,
David
On Fri, 2008-03-07 at 16:40 +0900, Soonho Kong wrote:
> Hello everyone. I'm a graduate student majoring in program analysis.
--
David Teller
Security of Distributed Systems
http://www.univ-orleans.fr/lifo/Members/David.Teller
Angry researcher: French Universities need reforms, but the LRU act
brings liquidations.
next prev parent reply other threads:[~2008-03-07 8:00 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 ` David Teller [this message]
2008-03-07 13:54 ` [Caml-list] " Christopher L Conway
2008-03-07 14:28 ` Gordon Henriksen
2008-03-31 9:51 ` Hendrik Tews
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=1204876856.6577.1.camel@Blefuscu \
--to=david.teller@univ-orleans.fr \
--cc=caml-list@yquem.inria.fr \
--cc=grad@ropas.snu.ac.kr \
--cc=kwang@ropas.snu.ac.kr \
--cc=soon@ropas.snu.ac.kr \
/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