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 mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104])
	by sympa.inria.fr (Postfix) with ESMTPS id 655057FA1F
	for <caml-list@sympa.inria.fr>; Fri, 11 Jul 2014 17:24:02 +0200 (CEST)
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  daniel.buenzli@erratique.ch) identity=pra;
  client-ip=74.55.86.74;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="daniel.buenzli@erratique.ch";
  x-sender="daniel.buenzli@erratique.ch";
  x-conformance=sidf_compatible
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  daniel.buenzli@erratique.ch) identity=mailfrom;
  client-ip=74.55.86.74;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="daniel.buenzli@erratique.ch";
  x-sender="daniel.buenzli@erratique.ch";
  x-conformance=sidf_compatible
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  postmaster@smtp.webfaction.com) identity=helo;
  client-ip=74.55.86.74;
  receiver=mail3-smtp-sop.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: AlQIAO0AwFNKN1ZKnGdsb2JhbABZhgmBIsVLAYEhDwEBAQEBBg0JCRQohAQBBSNWEAsaAiYCAkcQBhuIOq1HmHsXgSyNajMHgnc2gRYFogAYkE4
X-IPAS-Result: AlQIAO0AwFNKN1ZKnGdsb2JhbABZhgmBIsVLAYEhDwEBAQEBBg0JCRQohAQBBSNWEAsaAiYCAkcQBhuIOq1HmHsXgSyNajMHgnc2gRYFogAYkE4
X-IronPort-AV: E=Sophos;i="5.01,644,1400018400"; 
   d="scan'208";a="71108985"
Received: from mail6.webfaction.com (HELO smtp.webfaction.com) ([74.55.86.74])
  by mail3-smtp-sop.national.inria.fr with ESMTP; 11 Jul 2014 17:24:01 +0200
Received: from [172.17.156.176] (global-1-26.nat.csx.cam.ac.uk [131.111.184.26])
	by smtp.webfaction.com (Postfix) with ESMTP id E270C20E0E1B;
	Fri, 11 Jul 2014 15:23:59 +0000 (UTC)
Date: Fri, 11 Jul 2014 16:23:57 +0100
From: =?utf-8?Q?Daniel_B=C3=BCnzli?= <daniel.buenzli@erratique.ch>
To: Benjamin Canou <benjamin.canou@gmail.com>
Cc: caml-list@inria.fr
Message-ID: <9EF0E2E1119A470493E366AE6E7BF5F6@erratique.ch>
In-Reply-To: <53BFFADD.8030906@gmail.com>
References: <53BFE73E.6060106@gmail.com>
 <1F6CA9F698BB4509800C3FD280CE0ACB@erratique.ch>
 <53BFFADD.8030906@gmail.com>
X-Mailer: sparrow 1.6.4 (build 1178)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Subject: Re: [Caml-list] proposal for finding, loading and composing ppx
 preprocessors

Le vendredi, 11 juillet 2014 =C3=A0 15:55, Benjamin Canou a =C3=A9crit :
> Sure, the annotation mechanism itself is the core of what we propose.
> The ppx_loader is just a convenience utility to interpret them fully=20=20
> automatically. The tool you propose is another valid way to use them.=20=
=20
> We'll integrate it into ppx_loader as another option.

But if I understand correctly ppx_loader selectively applies ppxs on AST su=
bparts (?). If that the case you won't be able to provide matching function=
ality by simply listing the ppx to use on the command line, which would app=
ly each ppx on the whole file.=20=20

(which illustrates the fundamental uncomposable nature of these things).

Best,

Daniel
=20=20