caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Florent.Ouchet@imag.fr
To: Martin Jambon <martin.jambon@ens-lyon.org>
Cc: florent.ouchet@imag.fr, 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 20:59:06 +0200	[thread overview]
Message-ID: <20100624205906.48451eor602oaf3u@webmail.imag.fr> (raw)
In-Reply-To: <4C2399B0.4060503@ens-lyon.org>

Martin Jambon <martin.jambon@ens-lyon.org> a écrit :
> I disagree.  The syntax is a new and optional feature.  Authors who  
> want their
> new code to compile with an earlier version of OCaml should simply  
> avoid using
> the new feature, as always.

The 3.12 version number is just minor increment. It should keep  
backward compatibility with the 3.x branch as much as possible.

> Finally we'll be able to use pattern matching on records for real and it's
> really cool.  That means we can use records where we used to prefer tuples,
> typically on things like tree nodes.  It will make it easier to add fields
> when the code evolves, compared to tuples.

Yes, this feature is cool. We agree on this point. However not all  
systems will be updated to 3.12 as soon as the final version is out.  
Most users rely on their linux distribution ocaml (Debian stable is  
still stuck at 3.10 for instance).

For syntax sugar extensions, such as { loc; name; _ }, your "don't use  
it" conclusion can be understood. But for code stabilization syntax  
extensions, such as { ... ; _ }, it's an other story. Users stuck with  
more stable versions of the compiler should be able to use more stable  
versions of software compiled with it.

- Florent


  reply	other threads:[~2010-06-24 18:59 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 [this message]
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
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=20100624205906.48451eor602oaf3u@webmail.imag.fr \
    --to=florent.ouchet@imag.fr \
    --cc=caml-list@inria.fr \
    --cc=damien.doligez@inria.fr \
    --cc=martin.jambon@ens-lyon.org \
    /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).