caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Serge Sivkov <ssp.mryau@gmail.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] PPX is harmful to our community in the long term
Date: Sat, 22 Apr 2017 18:49:15 +0600	[thread overview]
Message-ID: <CAOUGqWx3+y5vP2WnxYeGazkexqEndcyEgfO=Jobo5qocs6t0Hw@mail.gmail.com> (raw)
In-Reply-To: <87d1c55pbx.fsf@rochefort>

[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]

Hence, my two cents: PPX has problems in cross-compilation use cases, but I
suppose something like new tag in META can reslove this issue.
As for me, just ppx_deriving* by whitequark is yet one example of
usefullness of PPX.

WBR, ssp

2017-04-22 5:10 GMT+06:00 Emilio Jesús Gallego Arias <e@x80.org>:

> "Hongbo Zhang (BLOOMBERG/ 731 LEX)" <hzhang295@bloomberg.net> writes:
>
> > Yes, that's exactly what I suggested in the beginning!
>
> Maybe I interpret the word "harmful" differently, but IMVHO I have to
> strongly disagree with your choice of subject in the original mail.
>
> Not only PPX has not been harmful for me, but it has been a life-saver
> tool that has enabled significant progress towards more productive
> research.
>
> "Hongbo Zhang (BLOOMBERG/ 731 LEX)" <hzhang295@bloomberg.net> writes:
>
> > calling it 'madness' is disrespectful
>
> Personally, I fully subscribe Yaron's message and I see nothing
> disrespectful in suggesting that abandoning syntactic abstractions is a
> very bad idea.
>
> You wrote:
>
>  "the OCaml library developer should avoid PPX as much as you can",
>
> but if you meant:
>
>  "PPX seems quite unstable these days, I wonder how could we improve
>   long-term stability?"
>
> I'd have to admit that message didn't reach to me.
>
> Best regards!
> Emilio
>
> --
> 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: 2600 bytes --]

  reply	other threads:[~2017-04-22 12:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21 21:48 Hongbo Zhang (BLOOMBERG/ 731 LEX)
2017-04-21 23:10 ` Emilio Jesús Gallego Arias
2017-04-22 12:49   ` Serge Sivkov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-04-23  0:06 Hongbo Zhang (BLOOMBERG/ 731 LEX)
2017-04-23  1:25 ` Yaron Minsky
2017-04-22 14:47 Hongbo Zhang (BLOOMBERG/ 731 LEX)
2017-04-22 19:47 ` Robert Muller
2017-04-23  1:30   ` Yaron Minsky
2017-04-21 19:23 Hongbo Zhang (BLOOMBERG/ 731 LEX)
2017-04-21 21:17 ` Fabrice Le Fessant
2017-04-28 11:07   ` Olaf Hering
2017-04-28 13:04     ` Anil Madhavapeddy
2017-04-28 14:50       ` Yaron Minsky
2017-04-28 14:55         ` Jacques Carette
2017-05-11  9:37           ` Jeremie Dimino
2017-04-21 15:41 Hongbo Zhang (BLOOMBERG/ 731 LEX)
2017-04-21 16:04 ` Yotam Barnoy
2017-04-21 16:43   ` Gerd Stolpmann
2017-04-21 17:11   ` Alain Frisch
2017-04-21 18:28     ` Jeremie Dimino
2017-04-21 16:55 ` Francois BERENGER
2017-04-21 19:11 ` Yaron Minsky
2017-04-21 19:22 ` Emilio Jesús Gallego Arias

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='CAOUGqWx3+y5vP2WnxYeGazkexqEndcyEgfO=Jobo5qocs6t0Hw@mail.gmail.com' \
    --to=ssp.mryau@gmail.com \
    --cc=caml-list@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).