Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "Hezekiah M. Carty" <hcarty@atmos.umd.edu>
To: "Loup Vaillant" <loup.vaillant@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: The OCaml Community (aka back from the Developer Days)
Date: Mon, 28 Jan 2008 15:46:39 -0500	[thread overview]
Message-ID: <3a360f590801281246nf1e5e3eg27fa31b55ba2ecab@mail.gmail.com> (raw)
In-Reply-To: <6f9f8f4a0801281235s136f53b4qae8ec2c928f931c@mail.gmail.com>

On Jan 28, 2008 3:35 PM, Loup Vaillant <loup.vaillant@gmail.com> wrote:
> 2008/1/28, Hezekiah M. Carty <hcarty@atmos.umd.edu>:
> > On Jan 28, 2008 2:49 PM, Jon Harrop <jon@ffconsultancy.com> wrote:
> > > On Monday 28 January 2008 15:43:22 Sylvain Le Gall wrote:
> > > > On 28-01-2008, Jon Harrop <jon@ffconsultancy.com> wrote:
> > > > > On Monday 28 January 2008 13:35:34 Sylvain Le Gall wrote:
> > > > >> I think we don't have discuss about dropping what is currently in the
> > > > >> standard library. INRIA will keep everything.
> > > > >> ...
> > > > >> Nobody will thrown the standard library.
> > > > >
> > > > > So we cannot fix the stdlib?
> > > >
> > > > Yep, this is what is called "bug compatible" library... But you can
> > > > create one on your own and remove the one from INRIA (hints
> > > > -nopervasives on your compiler command line).
> > >
> > > Then I don't understand how this improves upon the current situation.
> > >
> >
> > My understanding is that the benefits would come from having a richer,
> > community developed "official" OCaml distribution.  So the stdlib
> > would stay in place, but extra items would be included as well.  For
> > example, package ExtLib and some commonly useful Camlp4 extensions
> > along with the distribution .tar.gz/.exe/.dmg.  If I understood the
> > meeting transcription in IRC, the official OCaml folks at INRIA would
> > bless this as the proper way to get and install OCaml once the
> > community structure is in place.
>
> Could a patched version of the stdlib and/or compiler could be bundled
> in such a distribution? This is the only way to have a tail recursive
> List.map, for instance.
>
> I suppose working around the license can be done without too much
> hassle? If I understand, the distro maker have to distribute the
> unmodified sources and the patches, so the user have to first apply
> the patches, then compile whats need to be (possibly using a script to
> automate the whole process).
>
> Loup
>

The library license is LGPL, so the stdlib could be changed in the
distribution without extra licensing trouble.  However, that is
probably not the way to go if we want to maintain bug-for-bug
compatibility.  For the example you mentioned, ExtLib already has a
tail recursive List.map, so if that were included it (or something
similar) in the official distribution then developers will know that
"open ExtList" will provide them with a tail recursive List.map
implementation without the end user having to install libraries out of
the official distribution.

I do not know the details of the compiler license (QPL) but I think
modifications would have to be distributed as patches and then applied
on the user's end.  I also do not know how this would affect binary
distributions of OCaml.

-- 
Hezekiah M. Carty
Graduate Research Assistant
University of Maryland
Department of Atmospheric and Oceanic Science


  parent reply	other threads:[~2008-01-28 20:46 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-27 13:09 David Teller
2008-01-28  0:38 ` [Caml-list] " Oliver Bandel
2008-01-28 11:27   ` David Teller
2008-01-28 13:42     ` Sylvain Le Gall
2008-01-28 16:38       ` [Caml-list] " Andrej Bauer
2008-01-29  0:26         ` Markus Mottl
2008-01-29 13:45           ` Gerd Stolpmann
2008-01-29 20:07             ` Markus Mottl
2008-01-30 13:04             ` Kuba Ober
2008-01-30 13:26               ` Jon Harrop
2008-01-30 14:17                 ` Kuba Ober
2008-01-30 15:14                   ` Jon Harrop
2008-01-30 16:26                     ` Kuba Ober
2008-01-30 17:41                   ` [Caml-list] Re: The OCaml Community (aka back fromthe " David Allsopp
2008-01-30 21:32                     ` Kuba Ober
2008-01-30 13:10             ` [Caml-list] Re: The OCaml Community (aka back from the " Vincent Hanquez
2008-01-30  9:22           ` Sylvain Le Gall
2008-01-28 17:25     ` [Caml-list] " Peng Zang
2008-01-28 13:35   ` Sylvain Le Gall
2008-01-28 15:25     ` [Caml-list] " Jon Harrop
2008-01-28 15:43       ` Sylvain Le Gall
2008-01-28 19:49         ` [Caml-list] " Jon Harrop
2008-01-28 20:16           ` Hezekiah M. Carty
2008-01-28 20:35             ` Jon Harrop
2008-01-28 20:48               ` Hezekiah M. Carty
     [not found]             ` <6f9f8f4a0801281235s136f53b4qae8ec2c928f931c@mail.gmail.com>
2008-01-28 20:46               ` Hezekiah M. Carty [this message]
2008-01-28 21:29             ` Alterlib? (was "Re: The OCaml Community") Dario Teixeira
2008-01-28 21:48               ` [Caml-list] " blue storm
2008-01-28 13:52 ` [Caml-list] The OCaml Community (aka back from the Developer Days) Romain Beauxis
2008-01-28 14:42   ` Sylvain Le Gall
2008-01-28 15:39     ` [Caml-list] " Romain Beauxis
2008-01-28 15:49       ` Sylvain Le Gall
2008-01-28 15:56         ` [Caml-list] " Romain Beauxis
2008-01-29 15:23     ` Stefano Zacchiroli

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=3a360f590801281246nf1e5e3eg27fa31b55ba2ecab@mail.gmail.com \
    --to=hcarty@atmos.umd.edu \
    --cc=caml-list@inria.fr \
    --cc=loup.vaillant@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