From: Christophe Raffalli <raffalli@univ-savoie.fr>
To: caml-list@inria.fr
Subject: [Caml-list] proposal for library
Date: 21 Jun 2002 18:16:26 +0200 [thread overview]
Message-ID: <1024676186.1454.28.camel@d85.lama.univ-savoie.fr> (raw)
In-Reply-To: <20020620234233E.yoriyuki@mbg.sphere.ne.jp>
Le jeu 20/06/2002 à 16:42, YAMAGATA yoriyuki a écrit :
> From: Markus Mottl <markus@oefai.at>
> Subject: Re: [Caml-list] Unix.file_descr -> int ???
> Date: Thu, 20 Jun 2002 13:52:37 +0200
>
> > It might be a good idea to define some set of rules that allows people
> > external to INRIA to write libraries in such a way that they could be
> > accepted in the standard distribution.
>
> and some degree of disclosure of the future development plan, or at
> least, what INRIA team is working now, would help. This would reduce
> danger of duplicated works.
Why not have a system of submission/referee for adding functions to
existing library (I am often mising for instance the usual List.flat_map
or List.rev_append in list.mli) or adding new library to the standard
OCaml ?
There should exist some clearly written rules to respect, and the
referees should check that these rules are respected. The referees could
also ask for modification and so on ..
I do not think the INRIA team spend a lot of time adapting the libraries
when they do incompatible change to OCaml. And moreover, some libraries
could be maintained outside of INRIA (by the guy who created the
library) ?
I think this is interesting, because we often write some small library
of function that could be useful to every body ... so it is a nice way
to share them.
among the useful missing library that I am sure many people have
allready written, there are: library for multiset (using Map or
something better), partial order, etc ...
Morever, people could also submit optimized replacement for existing
libraries (using a compatible interface ans semantics, this is hard to
check for the referre). So this way we could get nice, complete and
efficient libraries for OCaml !
--
Christophe Raffalli
Université de Savoie
Batiment Le Chablais, bureau 21
73376 Le Bourget-du-Lac Cedex
tél: (33) 4 79 75 81 03
fax: (33) 4 79 75 87 42
mail: Christophe.Raffalli@univ-savoie.fr
www: http://www.lama.univ-savoie.fr/~RAFFALLI
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-06-21 19:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 13:38 [Caml-list] Unix.file_descr -> int ??? Alessandro Baretta
[not found] ` <000101c21705$d9f23640$0501a8c0@lexifi01>
2002-06-18 22:41 ` Alessandro Baretta
2002-06-19 16:22 ` John Max Skaller
2002-06-20 11:23 ` Xavier Leroy
2002-06-20 11:52 ` Markus Mottl
2002-06-20 13:14 ` Alessandro Baretta
2002-06-20 13:23 ` Stefano Lanzavecchia
2002-06-20 16:22 ` Alessandro Baretta
2002-06-20 14:42 ` YAMAGATA yoriyuki
2002-06-21 16:16 ` Christophe Raffalli [this message]
2002-06-22 11:56 ` [Caml-list] proposal for library Nicolas Cannasse
2002-07-08 10:42 Diego Olivier Fernandez Pons
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=1024676186.1454.28.camel@d85.lama.univ-savoie.fr \
--to=raffalli@univ-savoie.fr \
--cc=caml-list@inria.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