From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Parsing
Date: Sun, 24 Jun 2007 18:17:29 +0100 [thread overview]
Message-ID: <200706241817.29419.jon@ffconsultancy.com> (raw)
In-Reply-To: <678F32CA-B60D-49B3-AE42-450A53A5C6A8@vub.ac.be>
Thanks for the help!
On Friday 22 June 2007 11:14:56 Bruno De Fraine wrote:
> Another reason to use camlp4 Grammars is that you get automatic
> syntax error descriptions. However, this seems to contain bugs in the
> current camlp4:
I think the documentation is a bit out of date as well. I found that this
compile line works:
ocamlopt -pp camlp4of -I +camlp4 camlp4lib.cmxa -c tinyml.ml
Looks great though!
--
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-24 17:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 23:14 Parsing Jon Harrop
2007-06-21 23:26 ` [Caml-list] Parsing Jonathan Bryant
2007-06-21 23:45 ` Christian Stork
2007-06-22 4:03 ` skaller
2007-06-22 10:14 ` Bruno De Fraine
2007-06-24 17:17 ` Jon Harrop [this message]
2012-02-11 2:07 malc
2012-02-11 2:25 ` Ashish Agarwal
2012-02-11 17:41 ` Esther Baruk
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=200706241817.29419.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).