From: "François Bobot" <francois.bobot@cea.fr>
To: Yaron Minsky <yminsky@janestreet.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [ANN] Core Suite 111.17.00
Date: Wed, 18 Jun 2014 14:57:07 +0200 [thread overview]
Message-ID: <53A18CA3.7030402@cea.fr> (raw)
In-Reply-To: <CACLX4jTpROcFxSu2xw88q9_SwqzUY89C9ShvhkP4EepkVfXh-w@mail.gmail.com>
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
next prev parent reply other threads:[~2014-06-18 12:57 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 [this message]
2014-06-18 16:23 ` Yaron Minsky
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=53A18CA3.7030402@cea.fr \
--to=francois.bobot@cea.fr \
--cc=caml-list@inria.fr \
--cc=yminsky@janestreet.com \
/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