From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Dypgen C++ grammar
Date: Tue, 26 Jun 2007 07:45:48 +0100 [thread overview]
Message-ID: <200706260745.48713.jon@ffconsultancy.com> (raw)
In-Reply-To: <1182839924.13033.93.camel@rosella.wigram>
On Tuesday 26 June 2007 07:38:44 skaller wrote:
> The bottom line is that I want code written in Ocaml
> because I'm sooooo sick of portability hassles.. :)
Perhaps your best bet is to translate an existing grammar into OCaml:
http://www.computing.surrey.ac.uk/research/dsrg/fog/CxxLexer.l
http://www.computing.surrey.ac.uk/research/dsrg/fog/CxxTester.y
That is only 1,320 LOC.
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
The OCaml Journal
http://www.ffconsultancy.com/products/ocaml_journal/?e
next prev parent reply other threads:[~2007-06-26 6:51 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
2007-06-26 6:45 ` Jon Harrop [this message]
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=200706260745.48713.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--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;
as well as URLs for NNTP newsgroup(s).