From: Richard Jones <rich@annexia.org>
To: Jacques Carette <carette@mcmaster.ca>
Cc: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Using camlp4 in extensions
Date: Mon, 15 Dec 2008 15:24:47 +0000 [thread overview]
Message-ID: <20081215152447.GA11765@annexia.org> (raw)
In-Reply-To: <494663F2.7090409@mcmaster.ca>
On Mon, Dec 15, 2008 at 09:04:34AM -0500, Jacques Carette wrote:
> Question: is there a way to use a camlp4 extension *inside* the
> definition of another?
>
> AFAIK, extensions are not ordered, so trying to use camlp4 to deal with
> IFDEF in the source of a syntax extension (like pa_monad) to switch
> between 3.10 and 3.11 [to deal with the new private and lazy features]
> does not seem possible. Or have I missed something?
camlp4 extensions should be composable (as long as they don't actually
conflict with each other). Just list several *.cmo files on the
camlp4 command line. What happened when you tried it?
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2008-12-15 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 14:04 Jacques Carette
2008-12-15 15:24 ` Richard Jones [this message]
2008-12-15 16:10 ` [Caml-list] " Mauricio Fernandez
2008-12-15 16:15 ` Jacques Carette
2008-12-15 16:38 ` blue storm
2008-12-15 22:13 ` Stefano Zacchiroli
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=20081215152447.GA11765@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=carette@mcmaster.ca \
/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).