caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: tab@snarc.org (Vincent Hanquez)
To: Jonathan Bryant <watersofmemory@gmail.com>
Cc: Jon Harrop <jon@ffconsultancy.com>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] [OSR] Caml Community Code
Date: Fri, 1 Feb 2008 20:49:16 +0100	[thread overview]
Message-ID: <20080201194916.GB11881@snarc.org> (raw)
In-Reply-To: <b256a4c50802011100m1c4680dej98e9a90d4d75efda@mail.gmail.com>

On Fri, Feb 01, 2008 at 02:00:19PM -0500, Jonathan Bryant wrote:
>  I think that backwards-incompatibility, despite what INRIA may say, is not
> terribly important.  Let us not forget that they set a precedent when they
> released a incompatible and scantily documented, yet significantly improved,
> CamlP4 unannounced in 3.10.
> 
> I think that if the community wrote a new, significantly improved but
> incompatible standard library and handed it to INRIA, INRIA would be hard
> pressed to find a reason not to release an backwards-incompatible Caml 4.0,
> given there was a configure switch when building the compiler to build it
> using a frozen 3.x library, which was not possible 3.9 -> 3.10.  After all,
> incompatibilities are what major version numbers are for.
> 
> >From then on, the OCaml team could ship a language only tarball (plus
> compatability library) and concentrate on exactly what they are good at:
> writing a great implementation of OCaml, without us bugging them about
> improving the library.  All of the package managers being discussed could
> pull the language from INRIA and the "new" stdlib from wherever it is housed
> and automagically put the two together.

I just want to say that I really agree with this vision as well.
That's the only way this ocaml community thing is going to work IMHO.

-- 
Vincent Hanquez


  reply	other threads:[~2008-02-01 19:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 14:28 Jonathan Bryant
2008-01-31 16:25 ` [Caml-list] " blue storm
2008-01-31 20:53   ` Stefano Zacchiroli
2008-01-31 21:38     ` Jon Harrop
2008-02-01  8:13       ` Stefano Zacchiroli
2008-02-01  9:14         ` Jon Harrop
2008-02-01 13:56           ` Christopher L Conway
2008-02-01 15:50             ` Sylvain Le Gall
2008-02-01 18:07             ` [Caml-list] " Jon Harrop
2008-02-01 19:00               ` Jonathan Bryant
2008-02-01 19:49                 ` Vincent Hanquez [this message]
2008-02-01 20:41               ` Christopher L Conway
2008-02-04 14:35               ` Jean-Marc EBER
2008-02-04 17:35                 ` Jon Harrop
2008-01-31 17:47 ` Ashish Agarwal
2008-01-31 18:12   ` Jonathan Bryant
2008-02-01 17:26 ` David Allsopp
2008-02-01 18:27   ` Jonathan Bryant
2008-02-01 18:25     ` Jon Harrop
2008-02-03 12:21       ` David Teller
2008-01-31 15:57 Jonathan Bryant
2008-01-31 16:08 ` [Caml-list] " Romain Beauxis
2008-01-31 16:23   ` Jonathan Bryant

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=20080201194916.GB11881@snarc.org \
    --to=tab@snarc.org \
    --cc=caml-list@yquem.inria.fr \
    --cc=jon@ffconsultancy.com \
    --cc=watersofmemory@gmail.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;
as well as URLs for NNTP newsgroup(s).