From: Martin Jambon <martin_jambon@emailuser.net>
To: mulhern <mulhern@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] camlp4 behavior
Date: Sun, 5 Jun 2005 20:05:44 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0506052001400.2372-100000@localhost> (raw)
In-Reply-To: <54f15b6e05060519503a3d30d2@mail.gmail.com>
On Sun, 5 Jun 2005, mulhern wrote:
> Why does camlp4 fail to parse mLast.mli when invoked in the following way:
>
> camlp4 -I /usr/local/godi/lib/ocaml/std-lib/camlp4 pa_o.cmo
> /usr/local/godi/lib/ocaml/std-lib/camlp4/mLast.mli
> File "/usr/local/godi/lib/ocaml/std-lib/camlp4/mLast.mli", line 22,
> characters 46-47:
> Parse error: [interf] expected after [sig_item_semi] (in [interf])
> Uncaught exception: Stream.Error("[interf] expected after
> [sig_item_semi] (in [interf])")
Because it was written in the revised syntax: you should use pa_r.cmo
instead of pa_o.cmo, or directly camlp4r (man camlp4).
Martin
--
Martin Jambon, PhD
http://martin.jambon.free.fr
prev parent reply other threads:[~2005-06-06 3:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 2:50 mulhern
2005-06-06 3:05 ` Martin Jambon [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=Pine.LNX.4.44.0506052001400.2372-100000@localhost \
--to=martin_jambon@emailuser.net \
--cc=caml-list@yquem.inria.fr \
--cc=mulhern@gmail.com \
/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