From: Aaron Bohannon <bohannon@seas.upenn.edu>
To: caml-list@inria.fr
Subject: [Caml-list] Compiling with camlp4 extensions
Date: Fri, 22 Jun 2012 11:53:33 -0400 [thread overview]
Message-ID: <CANghceazTOEH5yGki4E14SDqK1y=nXMkvjF=5XSp5p+FPc7ydg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 451 bytes --]
Hi,
I have been trying to use the new camlp4 to write an OCaml syntax
extension. All the examples I have seen so far suggest that I use the
extension by passing ocamlc the "-pp" option. But it seems that all the
location info for error messages gets lost when I do this unless I catch
and report the parse error myself within the extension. Is there some way
to get ocamlc to report the parse error at the correct location
automatically?
- Aaron
[-- Attachment #2: Type: text/html, Size: 486 bytes --]
next reply other threads:[~2012-06-22 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 15:53 Aaron Bohannon [this message]
2012-06-22 16:36 ` Gabriel Scherer
2012-06-23 0:43 ` Aaron Bohannon
2012-06-23 9:42 ` Gabriel Scherer
2012-06-23 13:41 ` Aaron Bohannon
2012-06-23 17:39 ` Gabriel Scherer
2012-06-22 18:01 ` [Caml-list] " Hongbo Zhang
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='CANghceazTOEH5yGki4E14SDqK1y=nXMkvjF=5XSp5p+FPc7ydg@mail.gmail.com' \
--to=bohannon@seas.upenn.edu \
--cc=caml-list@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).