From: "Loup Vaillant" <loup.vaillant@gmail.com>
To: "Caml List" <caml-list@inria.fr>
Subject: Porting camlp4 stuff from 3.09 to 3.10: need help
Date: Wed, 9 Apr 2008 11:46:52 +0200 [thread overview]
Message-ID: <6f9f8f4a0804090246v19f42f3fgfe22a65f48f1f18b@mail.gmail.com> (raw)
Hello,
I am currently porting code which uses camlp4 from 3.09 to 3.10, and I
am quite stuck.
I would like to know if there is a document which describes the
compatibility breaking differences between the two versions. (The wiki
doesn't seem to have it yet).
It would also help me to know of the predefined quotations, (<:expr<
>>, <:str_item< >>, and such) and what they allow.
For now, I am stuck on this error:
File "pa_ocamlconf.ml", line 78, characters 14-21:
While expanding quotation "str_item" in a position of "expr":
Parse error: illegal begin of quotation of structure item
The mentioned line 78 is:
<:str_item< declare end >>
It looks like the "declare end" construct is not allowed any more. Is
there any equivalent in 3.10, and is there a specific bit of
documentation about this?
Thanks,
Loup
next reply other threads:[~2008-04-09 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 9:46 Loup Vaillant [this message]
2008-04-09 12:47 ` [Caml-list] " Richard Jones
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=6f9f8f4a0804090246v19f42f3fgfe22a65f48f1f18b@mail.gmail.com \
--to=loup.vaillant@gmail.com \
--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