From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Dario Teixeira <dario.teixeira@nleyten.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] META file standards for ppx extensions
Date: Thu, 09 Apr 2015 18:51:14 +0200 [thread overview]
Message-ID: <1428598274.4056.111.camel@thinkpad.lan.sumadev.de> (raw)
In-Reply-To: <02a4b13213003ff9d702faa07ff98b6e@nleyten.com>
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
Am Donnerstag, den 09.04.2015, 17:28 +0100 schrieb Dario Teixeira:
> Hi,
>
> > How do you compose ppx extensions using META? Can you require
> > "barloot.ppx"? The camlp4 "syntax" packages are usual ocaml
> > libraries, so the rules of composition are (almost) clear.
> > How does it work when you want to compose ppx rewriters?
>
> Gerd can provide a more authoritative answer, but I reckon
> ocamlfind is smart enough to handle such cases. You can
> already require a sub-package after all, and involving ppx
> should not change this.
As ppx rewriters are commands, and as you can specify the -ppx option
several times to invoke several commands, the answer should be as clear
as for the library case: The commands are just run one after the other,
and if there is a dependency "ppx1 requires ppx2", the command for ppx2
is run first.
Gerd
--
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany gerd@gerd-stolpmann.de
My OCaml site: http://www.camlcity.org
Contact details: http://www.camlcity.org/contact.html
Company homepage: http://www.gerd-stolpmann.de
------------------------------------------------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-04-09 16:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 18:20 Dario Teixeira
2015-04-08 18:59 ` Drup
2015-04-08 19:59 ` Dario Teixeira
2015-04-08 20:37 ` Daniel Bünzli
2015-04-09 10:07 ` Dario Teixeira
2015-04-09 10:56 ` Gerd Stolpmann
2015-04-09 12:24 ` Dario Teixeira
2015-04-09 15:33 ` Daniel Bünzli
2015-04-09 16:45 ` Gerd Stolpmann
2015-04-09 17:27 ` Daniel Bünzli
2015-04-09 18:05 ` Daniel Bünzli
2015-04-09 22:26 ` Gerd Stolpmann
2015-04-09 22:21 ` Gerd Stolpmann
2015-04-09 23:06 ` Daniel Bünzli
2015-04-10 8:53 ` François Bobot
2015-04-10 9:42 ` Daniel Bünzli
2015-04-10 10:09 ` Alain Frisch
2015-04-10 11:45 ` Thomas Gazagnaire
2015-04-10 11:04 ` François Bobot
2015-04-10 11:55 ` Daniel Bünzli
2015-04-10 16:33 ` François Bobot
2015-04-10 17:43 ` Daniel Bünzli
2015-04-12 6:00 ` Anil Madhavapeddy
2015-04-10 11:25 ` Gerd Stolpmann
2015-04-10 11:55 ` Daniel Bünzli
2015-04-09 15:45 ` Thomas Gazagnaire
2015-04-09 16:28 ` Dario Teixeira
2015-04-09 16:51 ` Gerd Stolpmann [this message]
2015-04-10 12:23 ` Daniel Bünzli
2015-04-10 14:55 ` Gerd Stolpmann
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=1428598274.4056.111.camel@thinkpad.lan.sumadev.de \
--to=info@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=dario.teixeira@nleyten.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