caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Pierre Weis <Pierre.Weis@inria.fr>
To: Markus Mottl <mottl@miss.wu-wien.ac.at>
Cc: caml-list@inria.fr
Subject: Re: additions to standard library?
Date: Tue, 14 Mar 2000 18:53:41 +0100	[thread overview]
Message-ID: <20000314185341.44483@pauillac.inria.fr> (raw)
In-Reply-To: <200003120239.DAA18581@miss.wu-wien.ac.at>; from Markus Mottl on Sun, Mar 12, 2000 at 03:39:21AM +0100

> It is also not my intention to get over-featured libraries. I was just
> wondering which would be the best way to propose reasonable additions
> and/or contribute code. I am not out for a specific way to do this - I just
> would like to know which way would be most appropriate for INRIA. It would
> be disappointing for both sides if unwise decisions in this respect lead to
> something like "diverging development".
> 
> At the moment I have the feeling that some modules are indeed rather
> under-featured. One can really not say that e.g. the "Char"-module boasts
> with rich features, and some others (like the mentioned Set-module) would
> also not suffer if functions like "partition" or "for_all", etc., are
> added, especially considering the fact that these "settish" functions even
> exist in the List-module.

You're right: for the time being our libraries are in some sense
minimalist (due to the ancient times problems with memory capacities
of micro computers and 1.4 Mb floppies). It may be time now to get
reasonably featured libraries. For instance, you mentioned few
functions that sound adequate to be added (in the first place because
there are not a zillion of them).

> > On the other hand, I don't think it would be a bad thing if more
> > people contributed to the development of O'Caml.
> 
> Definitely! Though, there should be some standard way to contribute so that
> people don't step on each other's toes. Naturally, the opinion of the main
> developers should set the direction...
> 
> > Anyway, you can always set up a repository on Sourceforge or any
> > similar site and see what happens. :-)
> 
> I have thought about this, but I am not sure whether this provokes what you
> mentioned: that the "regular" and the "extended" library diverge. On the
> other hand, it seems that Sourceforge really provides for great features
> for free software projects (CVS-repository, mailing lists, bug tracking,
> patch manager, etc...), which would reduce at least the administrative
> effort on INRIA's side...

We also have the tools you mentioned to develop the Caml compiler
(``CVS-repository, mailing lists, bug tracking, patch manager,
etc...''), except may be ``etc...'':), so that there is no need to set
up another site to develop the Caml standard library (on the other
hand the use of SourceForge may be very relevant for other
cooperative developments out of the Caml compiler). In any means we
must avoid confusion and divergence with 2 different standard libraries.

Caml users may contribute to the wish list associated to the caml bugs
tracking system: you may contribute in a useful way if you also
provide the code associated to your wishes.

Best regards,

-- 
Pierre Weis

INRIA, Projet Cristal, http://pauillac.inria.fr/~weis



  parent reply	other threads:[~2000-03-14 18:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-07 15:24 Markus Mottl
2000-03-08 19:03 ` Jean-Christophe Filliatre
2000-03-08 22:29   ` Markus Mottl
2000-03-10 10:51     ` Christian RINDERKNECHT
2000-03-09 13:18 ` Thorsten Ohl
2000-03-10 10:04   ` Francisco Valverde Albacete
2000-03-10 20:33     ` Markus Mottl
2000-03-14 23:15       ` Max Skaller
2000-03-11 18:49     ` Brian Rogoff
2000-03-12  1:54 ` Jerome Vouillon
     [not found]   ` <200003120239.DAA18581@miss.wu-wien.ac.at>
2000-03-14 17:53     ` Pierre Weis [this message]
2000-03-10 17:55 Manuel Fahndrich
2000-03-14 17:24 Don Syme
2000-03-21 21:08 ` John Max Skaller
2000-03-21 21:43 Don Syme

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=20000314185341.44483@pauillac.inria.fr \
    --to=pierre.weis@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=mottl@miss.wu-wien.ac.at \
    /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).