From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 2FEC97FA1F for ; Fri, 11 Jul 2014 16:55:31 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of benjamin.canou@gmail.com) identity=pra; client-ip=74.125.82.49; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="benjamin.canou@gmail.com"; x-sender="benjamin.canou@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of benjamin.canou@gmail.com designates 74.125.82.49 as permitted sender) identity=mailfrom; client-ip=74.125.82.49; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="benjamin.canou@gmail.com"; x-sender="benjamin.canou@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-wg0-f49.google.com) identity=helo; client-ip=74.125.82.49; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="benjamin.canou@gmail.com"; x-sender="postmaster@mail-wg0-f49.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjYBABr6v1NKfVIxlGdsb2JhbABZgmqEQcVLAYELFg8BAQEBBwsLCRIqhAQBAQQSEQ8BBQgBGxwBAQMMBgULDwIFFgsCAgkDAgECARERAQUBHAYNAQcCHogLAQMRAQShKGqLJ4FygxCMDAoZJw1khjQRAQUOgR6OHQeCd4FMAQSWa4QakitBhHY X-IPAS-Result: AjYBABr6v1NKfVIxlGdsb2JhbABZgmqEQcVLAYELFg8BAQEBBwsLCRIqhAQBAQQSEQ8BBQgBGxwBAQMMBgULDwIFFgsCAgkDAgECARERAQUBHAYNAQcCHogLAQMRAQShKGqLJ4FygxCMDAoZJw1khjQRAQUOgR6OHQeCd4FMAQSWa4QakitBhHY X-IronPort-AV: E=Sophos;i="5.01,644,1400018400"; d="scan'208";a="71104806" Received: from mail-wg0-f49.google.com ([74.125.82.49]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 11 Jul 2014 16:55:30 +0200 Received: by mail-wg0-f49.google.com with SMTP id k14so503399wgh.20 for ; Fri, 11 Jul 2014 07:55:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=gYLBM8gtvaVhvdJx+sRUmV6LVNkNoK1t8OH2ghyKKK0=; b=kn7q3RDvo4PzAXXYCSrUPiAngkjDP2Ae8DaLbR98EmKuzepV+I0/JiShtx22iqhV+n 47S2iUuc9tyYWEZaKF9VE0OLXfcsTZi2esuCV89GPS4PZi3UKbuYNrvduonOq8a8zGAc VoCbGOttEsyaTCSSYe1EY9dlA3TnZkZmIPzTEvryallquwOjFD1z+ABvPuxMNr+KPAd+ dnWLHRfctR2CSjR4QF+fOswIq9LA7veZO+TmHxQLcNDphF94T3s7QlNuAuYKdMHVm3rX mKphjzoF7RBHfoJVODqpd3Kulrh5yQpzBagSu+8OCvgm5gOVcNFqry025+vFggAfY1DT 20dg== X-Received: by 10.180.108.1 with SMTP id hg1mr5688931wib.25.1405090528432; Fri, 11 Jul 2014 07:55:28 -0700 (PDT) Received: from ?IPv6:2001:660:3013:3:9eb6:54ff:fea5:8a99? ([2001:660:3013:3:9eb6:54ff:fea5:8a99]) by mx.google.com with ESMTPSA id jb16sm8280787wic.10.2014.07.11.07.55.27 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 11 Jul 2014 07:55:27 -0700 (PDT) Message-ID: <53BFFADD.8030906@gmail.com> Date: Fri, 11 Jul 2014 16:55:25 +0200 From: Benjamin Canou User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Icedove/30.0 MIME-Version: 1.0 To: =?UTF-8?B?RGFuaWVsIELDvG56bGk=?= CC: caml-list@inria.fr References: <53BFE73E.6060106@gmail.com> <1F6CA9F698BB4509800C3FD280CE0ACB@erratique.ch> In-Reply-To: <1F6CA9F698BB4509800C3FD280CE0ACB@erratique.ch> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [Caml-list] proposal for finding, loading and composing ppx preprocessors Le 11/07/2014 16:21, Daniel Bünzli a écrit : > > What do you think ? > If I understand correctly this is a ppx for selectively using ppxs over a file. Bonus points for the higher-order ppx. > > Since apparently we have to deal with this crap until we actually get something decent for static meta programming in this language, wouldn't it be easier to just define a standard annotation as you suggest, and then have some kind of "ppxdep" tool that just spits you the flags you will have to put on the command line in order to be able to compile it ? > Sure, the annotation mechanism itself is the core of what we propose. The ppx_loader is just a convenience utility to interpret them fully automatically. The tool you propose is another valid way to use them. We'll integrate it into ppx_loader as another option. > Daniel > > P.S. What happens if I do [@@@ syntax "ppx_loader"] ? > It works wonders :) Benjamin.