From: Nicolas Ojeda Bar <nicolas.ojeda.bar@lexifi.com>
To: Francois Berenger <francois.berenger@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Is it possible to get back some OCaml code after ppx processing ?
Date: Wed, 23 Mar 2016 18:05:27 +0100 [thread overview]
Message-ID: <CADK7aFMsmz5a8sAt7QjMssNjPmppMVUA=Qas5nyc+5CAhmCa+Q@mail.gmail.com> (raw)
In-Reply-To: <56F2C6D7.3080707@inria.fr>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
Hi Francois,
You can use ppx_tools (https://github.com/alainfrisch/ppx_tools) to do it:
ocamlfind ppx_tools/rewriter ./my_ppx_rewriter foo.ml
Cheers,
Nicolas
On Wed, Mar 23, 2016 at 5:39 PM, Francois Berenger <
francois.berenger@inria.fr> wrote:
> Dear list,
>
> I am completely new to the -ppx option of the compiler, so please
> forgive in advance my (probably stupid) two questions.
>
> Here is some example code:
> ---
> type t = {
> i: int;
> f: float
> } [@@deriving sexp]
> ---
>
> 1) I'd like to see all the functions automatically created
> by the magical spell "[@@deriving sexp]".
> At least their names and type signatures would be nice.
> How to do that?
>
> 2) If that's not possible, I'd like to get back some
> OCaml code corresponding to the AST after ppx processing.
> If that's possible, how to do that?
>
> Thanks a lot,
> Francois.
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
[-- Attachment #2: Type: text/html, Size: 2007 bytes --]
prev parent reply other threads:[~2016-03-23 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 16:39 Francois Berenger
2016-03-23 17:02 ` Louis Roché
2016-03-24 9:27 ` Goswin von Brederlow
2016-03-24 10:37 ` Jeremie Dimino
2016-03-23 17:05 ` Nicolas Ojeda Bar [this message]
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='CADK7aFMsmz5a8sAt7QjMssNjPmppMVUA=Qas5nyc+5CAhmCa+Q@mail.gmail.com' \
--to=nicolas.ojeda.bar@lexifi.com \
--cc=caml-list@inria.fr \
--cc=francois.berenger@inria.fr \
/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).