From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Dario Teixeira <dario.teixeira@nleyten.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] META file standards for ppx extensions
Date: Wed, 8 Apr 2015 22:37:20 +0200 [thread overview]
Message-ID: <292F5F40C05A4B9BBEB96266F05F6FEB@erratique.ch> (raw)
In-Reply-To: <5297cdaceccd6db2a60700bf686ccfb7@nleyten.com>
It seems to me that Dario's scheme, that is always have PKG.ppx, is more forward looking. We could perfectly imagine that a library in the future will implement its functionality using another mechanism (for example in a non-ugly way, using a macro system).
We can imagine current packages that are using camlp4 providing both a legacy PKG.camlp4 and a PKG.ppx package.
It also makes it more clear in the build system specification what crap pre-processing technology is being pulled in.
Best,
Daniel
next prev parent reply other threads:[~2015-04-08 20:37 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 [this message]
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
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=292F5F40C05A4B9BBEB96266F05F6FEB@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--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