caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Florent Ouchet <florent.ouchet@imag.fr>
To: Till Varoquaux <till@pps.jussieu.fr>
Cc: Martin Jambon <martin.jambon@ens-lyon.org>,
	Damien Doligez <damien.doligez@inria.fr>,
	caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml 3.12.0+beta1
Date: Thu, 24 Jun 2010 22:49:44 +0200	[thread overview]
Message-ID: <20100624224944.91886zxkgzxq78iw@webmail.imag.fr> (raw)
In-Reply-To: <AANLkTikF5ksWbj8J-b6qJ0FNCSMXkCv-M9KN5p-rX8yU@mail.gmail.com>

Till Varoquaux <till@pps.jussieu.fr> a écrit :
> As for forward compatibility (ie programs coded with 3.12 in mind
> might not compile with 3.10) this is a price I am happy to pay in
> order to have a language that's constantly improving. I think that
> this is feeling that is shared by many.

ok all, it has to be considered as forward compatibility, speaking at  
ocaml point-of-view, this POV is likely the one most of you have.
However, at source POV (where OCaml is seen as a tool), this can be  
seen as backward compatibility: the source code we write could be  
backward compatible with older versions of OCaml. Anyway, I will stop  
here the terminology fight and use your POV...

> And, last but nor least, older does not necessarily mean more stable.

...and I won't feed the troll too.

> You seem to use those interchangeably in your mail. Windows 3.11 is
> old...

This specific ( { ; _} ) forward compatibility with ocaml <3.12 is  
possible for a little cost. It's just about removing the extra  
underscore characters. Anyway if the preprocessing script does not  
come out of the ocaml 3.12 box, I will have to do it. Other developers  
may have to so as well.
Mainly because this coverage check is a must-do and because I do not  
want to force a general update to OCaml 3.12 when that can be avoided.  
The coverage check has to be done only once, at "developer's" side,  
using 3.12. Once the changes are done, stripped code can easily be  
compiled using older versions of OCaml, at "user's" side.

- Florent


  reply	other threads:[~2010-06-24 20:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 13:07 Damien Doligez
2010-06-16 16:28 ` [Caml-list] " Yoann Padioleau
2010-06-16 18:40   ` Martin Jambon
2010-06-16 20:52 ` Török Edwin
2010-06-17 13:35   ` xclerc
2010-06-18 14:56     ` xclerc
2010-06-19  5:51 ` Stéphane Glondu
2010-06-24  9:38 ` Florent Ouchet
2010-06-24 17:45   ` Martin Jambon
2010-06-24 18:59     ` Florent.Ouchet
2010-06-24 19:29       ` Dmitry Bely
2010-06-24 19:31       ` Mathias Kende
2010-06-24 19:39       ` Till Varoquaux
2010-06-24 20:49         ` Florent Ouchet [this message]
2010-06-24 20:57           ` Hezekiah M. Carty
2010-06-24 22:05             ` Florent Ouchet
2010-06-25  5:54               ` bluestorm
2010-06-25  6:24                 ` Florent Ouchet
2010-06-25  8:17                   ` bluestorm
2010-06-25  8:48                     ` David Allsopp
2010-06-25  9:35                       ` bluestorm
2010-06-25  7:29 ` bluestorm

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=20100624224944.91886zxkgzxq78iw@webmail.imag.fr \
    --to=florent.ouchet@imag.fr \
    --cc=caml-list@inria.fr \
    --cc=damien.doligez@inria.fr \
    --cc=martin.jambon@ens-lyon.org \
    --cc=till@pps.jussieu.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).