caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yaron Minsky <yminsky@janestreet.com>
To: "François Bobot" <francois.bobot@cea.fr>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] Core Suite 111.17.00
Date: Wed, 18 Jun 2014 12:23:23 -0400	[thread overview]
Message-ID: <CACLX4jTtD-HZsgVu15Ex2TcSvvrSyYceVjpgpjG49SFcAw4q4g@mail.gmail.com> (raw)
In-Reply-To: <53A18CA3.7030402@cea.fr>

We actually had a discussion about this internally, and I was mostly
convinced that my transition plan is the wrong one --- that it's
probably better to leave the old camlp4 based syntax extensions as
they are, and just mothball them; leave them around, but stop
improving them.  And then people who want to use the new and
better-supported extensions will need to flip to using ppx.  And you
can use the camlp4-based solution to straddle the gap if you need to
support both new and old compilers.

y

On Wed, Jun 18, 2014 at 8:57 AM, François Bobot <francois.bobot@cea.fr> wrote:
> On 18/06/2014 11:28, Yaron Minsky wrote:
>> This change isn't really part of that transition, but that transition will likely be necessary.  My
>> sense is that the right thing is to rewrite the syntax extensions using extension points, and then
>> write a shim camlp4 extension that converts "with sexp" to the correct annotation.  That said, this
>> is a long and tricky process that won't happen immediately on 4.02's release.
>
> Thank you for the quick answer. That seems the right transition path for the code of a project, but
> I wonder what happen at a bigger scale.
>
> After the transition projects will need to support older versions of ocaml that perhaps don't have
> extension points. Moreover every projects will not do the transition at the same time.
>
> It seems, IMHO, that type-conv will have to work for the following cases transparently:
>
> - camlp4 (with ocaml < 4.02 or >= 4.02) old syntax
> - camlp4 (with ocaml < 4.02 or >= 4.02) new syntax
>
> - extension point (with ocaml >= 4.02) new syntax
>
>
> Do you agree with that? Do you think it is doable/maintainable until ocaml < 4.02 are not used anymore?
>
>
> Best,
>
> --
> François

  reply	other threads:[~2014-06-18 16:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17 16:43 Ben Millwood
2014-06-18  7:35 ` François Bobot
2014-06-18  9:28   ` Yaron Minsky
2014-06-18 12:57     ` François Bobot
2014-06-18 16:23       ` Yaron Minsky [this message]
2014-06-20  3:41         ` [Caml-list] mysterious cgi problem Eliot Handelman
2014-06-20  5:48           ` Siraaj Khandkar
2014-06-20  8:53             ` Mark Shinwell
2014-06-21 19:19           ` Eliot Handelman

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=CACLX4jTtD-HZsgVu15Ex2TcSvvrSyYceVjpgpjG49SFcAw4q4g@mail.gmail.com \
    --to=yminsky@janestreet.com \
    --cc=caml-list@inria.fr \
    --cc=francois.bobot@cea.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).