From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <daniel.buenzli@erratique.ch>
X-Original-To: caml-list@sympa.inria.fr
Delivered-To: caml-list@sympa.inria.fr
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83])
	by sympa.inria.fr (Postfix) with ESMTPS id 2A0EF7FCCB
	for <caml-list@sympa.inria.fr>; Wed,  8 Apr 2015 22:37:27 +0200 (CEST)
Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender
  authenticity information available from domain of
  daniel.buenzli@erratique.ch) identity=pra;
  client-ip=74.55.86.74;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="daniel.buenzli@erratique.ch";
  x-sender="daniel.buenzli@erratique.ch";
  x-conformance=sidf_compatible
Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender
  authenticity information available from domain of
  daniel.buenzli@erratique.ch) identity=mailfrom;
  client-ip=74.55.86.74;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="daniel.buenzli@erratique.ch";
  x-sender="daniel.buenzli@erratique.ch";
  x-conformance=sidf_compatible
Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender
  authenticity information available from domain of
  postmaster@smtp.webfaction.com) identity=helo;
  client-ip=74.55.86.74;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="daniel.buenzli@erratique.ch";
  x-sender="postmaster@smtp.webfaction.com";
  x-conformance=sidf_compatible
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DmAADQkCVVnEpWN0pch0vILwKBaBEBAQEBAQEBEQEBAQEBBg0JCRQuhCABAQQjVhALGgImAgJHEAYbiCIEtkCWTgEBAQcBAQEBHoEhigqEfAeCaC+BFgEEogIPjUWEE4MwAQEB
X-IPAS-Result: A0DmAADQkCVVnEpWN0pch0vILwKBaBEBAQEBAQEBEQEBAQEBBg0JCRQuhCABAQQjVhALGgImAgJHEAYbiCIEtkCWTgEBAQcBAQEBHoEhigqEfAeCaC+BFgEEogIPjUWEE4MwAQEB
X-IronPort-AV: E=Sophos;i="5.11,545,1422918000"; 
   d="scan'208";a="132257356"
Received: from mail6.webfaction.com (HELO smtp.webfaction.com) ([74.55.86.74])
  by mail2-smtp-roc.national.inria.fr with ESMTP; 08 Apr 2015 22:37:26 +0200
Received: from [172.20.10.2] (95.234.197.178.dynamic.wless.lssmb00p-cgnat.res.cust.swisscom.ch [178.197.234.95])
	by smtp.webfaction.com (Postfix) with ESMTP id 55D3120EEB97;
	Wed,  8 Apr 2015 20:37:23 +0000 (UTC)
Date: Wed, 8 Apr 2015 22:37:20 +0200
From: =?utf-8?Q?Daniel_B=C3=BCnzli?= <daniel.buenzli@erratique.ch>
To: Dario Teixeira <dario.teixeira@nleyten.com>
Cc: caml-list@inria.fr
Message-ID: <292F5F40C05A4B9BBEB96266F05F6FEB@erratique.ch>
In-Reply-To: <5297cdaceccd6db2a60700bf686ccfb7@nleyten.com>
References: <2f9c74beafcf41f3ab30324fb1ece739@nleyten.com>
 <55257AAD.6030004@zoho.com>
 <5297cdaceccd6db2a60700bf686ccfb7@nleyten.com>
X-Mailer: sparrow 1.6.4 (build 1178)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: [Caml-list] META file standards for ppx extensions

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