From: "Nicolas Cannasse" <warplayer@free.fr>
To: "fva" <fva@tsc.uc3m.es>, "Stefano Zacchiroli" <zack@bononia.it>
Cc: <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml standard library improvement
Date: Mon, 24 Feb 2003 10:21:02 +0900 [thread overview]
Message-ID: <003d01c2dba2$fef21ca0$1c13f9ca@Warp2> (raw)
In-Reply-To: <3E562F68.50503@tsc.uc3m.es>
> Why not (self?)appoint, say, three persons (I don't care about many more
> with decision power to come to an agreement about anything) to receive
> would-be code and maintain a "big-s(c)ale library"... This may find its
> way into the Standard library or it may not, but would definitely make
> happy all these people wanting to contribute differentially to the whole
> OCaml effort...
>
> Just an idea... Something to discuss...
I agree with that point of view.
Actually the C++ STL ( although C++ is not perhaps the better sample when
talking about programming languages... ) is distributed and developped
seperatly from compilers. Of course there is several compilers but...
Indeed perhaps we ( the ocaml programmers interested in developping the
"ocaml -extended- standard library" ) should only need a separate mailling
list ( to discuss about implementations choices such as tail recursive
calls ) and perhaps a CVS tree... so maybe a sourceforge project would be
nice here.
I would be more than happy to join such a project.
Nicolas Cannasse
-------------------
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:[~2003-02-24 1:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 18:03 [Caml-list] Hashtbl.keys Oliver Bandel
2003-02-18 18:13 ` Hal Daume III
2003-02-20 9:43 ` Xavier Leroy
2003-02-20 16:54 ` [Caml-list] OCaml standard library improvement Stefano Zacchiroli
2003-02-21 13:47 ` Nicolas George
2003-02-22 14:09 ` Stefano Zacchiroli
2003-02-23 18:33 ` Alessandro Baretta
2003-02-21 13:53 ` fva
2003-02-21 16:18 ` Amit Dubey
2003-02-21 17:10 ` Brian Hurt
2003-02-21 17:23 ` Nicolas George
2003-02-21 18:01 ` Brian Hurt
2003-02-21 18:57 ` Chris Hecker
2003-02-21 19:28 ` Brian Hurt
2003-02-22 15:52 ` John Max Skaller
2003-02-21 17:32 ` Maxence Guesdon
2003-02-24 1:21 ` Nicolas Cannasse [this message]
2003-02-24 1:45 ` Chris Hecker
2003-02-24 2:46 ` Brian Hurt
2003-02-24 7:42 ` Stefano Zacchiroli
2003-02-24 10:18 ` fva
2003-02-24 11:03 ` Amit Dubey
2003-02-24 12:56 ` John Max Skaller
2003-02-24 13:06 ` Lauri Alanko
2003-02-24 13:08 ` Sven Luther
2003-02-24 14:05 ` [Caml-list] Library Discussion Followups Amit Dubey
2003-02-25 5:49 ` [Caml-list] OCaml standard library improvement John Max Skaller
2003-02-25 8:29 ` Xavier Leroy
2003-02-24 16:50 ` Benjamin C. Pierce
2003-02-24 17:28 ` brogoff
2003-02-25 18:08 ` Diego Olivier Fernandez Pons
2003-02-26 7:47 ` Jean-Christophe Filliatre
2003-02-25 10:47 ` [Caml-list] OCaml standard library _improvement_ NOT a new library! Stefano Zacchiroli
2003-02-25 21:43 ` Alessandro Baretta
2003-02-26 9:42 ` Stefano Zacchiroli
2003-02-21 6:40 ` [Caml-list] Hashtbl.keys Alex Cowie
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='003d01c2dba2$fef21ca0$1c13f9ca@Warp2' \
--to=warplayer@free.fr \
--cc=caml-list@inria.fr \
--cc=fva@tsc.uc3m.es \
--cc=zack@bononia.it \
/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).