From: Benjamin Canou <benjamin.canou@gmail.com>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] proposal for finding, loading and composing ppx preprocessors
Date: Fri, 11 Jul 2014 18:00:16 +0200 [thread overview]
Message-ID: <53C00A10.5090008@gmail.com> (raw)
In-Reply-To: <9EF0E2E1119A470493E366AE6E7BF5F6@erratique.ch>
Le 11/07/2014 17:23, Daniel Bünzli a écrit :
> Le vendredi, 11 juillet 2014 à 15:55, Benjamin Canou a écrit :
>> 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.
> But if I understand correctly ppx_loader selectively applies ppxs on AST subparts (?). If that the case you won't be able to provide matching functionality by simply listing the ppx to use on the command line, which would apply each ppx on the whole file.
True enough. We could force the annotations to be placed at the
beginning of files. After all, the interest of selectively applying ppxs
to parts of files is not clear. The responsibility of deciding which
parts to rewrite probably belongs to each ppx and not ppx_loader.
next prev parent reply other threads:[~2014-07-11 16:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 13:31 Benjamin Canou
2014-07-11 14:21 ` Daniel Bünzli
2014-07-11 14:36 ` Peter Zotov
2014-07-11 14:49 ` Daniel Bünzli
2014-07-11 14:55 ` Peter Zotov
2014-07-11 14:52 ` Mark Shinwell
2014-07-11 15:27 ` Anil Madhavapeddy
2014-07-11 15:35 ` Mark Shinwell
2014-07-11 14:55 ` Benjamin Canou
2014-07-11 15:23 ` Daniel Bünzli
2014-07-11 16:00 ` Benjamin Canou [this message]
2014-07-11 16:13 ` Alain Frisch
2014-07-15 13:59 ` Benjamin Canou
2014-07-15 15:56 ` Alain Frisch
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=53C00A10.5090008@gmail.com \
--to=benjamin.canou@gmail.com \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@erratique.ch \
/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