caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Thomas Gazagnaire <thomas@gazagnaire.org>
To: Dario Teixeira <dario.teixeira@nleyten.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] META file standards for ppx extensions
Date: Thu, 9 Apr 2015 17:45:44 +0200	[thread overview]
Message-ID: <AFDE0073-F048-4A6C-B66F-9D57914B203D@gazagnaire.org> (raw)
In-Reply-To: <d8a23c877189537c81524be5df2b4377@nleyten.com>

Hi,

first I think it's a good idea to have a proper convention for ppx pre-processors. And I like your proposal. I just have a question, though:

>   package "syntax" (
>     version = "1.0"
>     description = "Camlp4-based syntax extension for Fooloot"
>     requires = "camlp4 fooloot"
>     archive(syntax, preprocessor) = "pa_fooloot.cma"
>     archive(syntax, toploop) = "pa_fooloot.cma"
>     archive(syntax, preprocessor, native) = "pa_fooloot.cmxa"
>     archive(syntax, preprocessor, native, plugin) = "pa_fooloot.cmxs"
>   )
> 
>   package "ppx" (
>     version = "1.0"
>     description = "New-style (ppx) syntax extension for Fooloot"
>     requires = "fooloot"
>     ppx = "ppx_fooloot"
>   )

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?

Thomas

  parent reply	other threads:[~2015-04-09 15:45 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 [this message]
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=AFDE0073-F048-4A6C-B66F-9D57914B203D@gazagnaire.org \
    --to=thomas@gazagnaire.org \
    --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;
as well as URLs for NNTP newsgroup(s).