Browse thread
[Caml-list] [ANN] The Missing Library
-
John Goerzen
-
Kenneth Knowles
- Alexander V. Voinov
-
John Goerzen
-
Maxence Guesdon
-
John Goerzen
- Maxence Guesdon
-
John Goerzen
-
Alain.Frisch@e...
-
John Goerzen
-
Alain.Frisch@e...
-
Nicolas Cannasse
-
Yamagata Yoriyuki
- Gerd Stolpmann
-
Nicolas Cannasse
-
Yamagata Yoriyuki
- Jacques GARRIGUE
- Nicolas Cannasse
-
Yamagata Yoriyuki
-
Yamagata Yoriyuki
-
Nicolas Cannasse
- oliver@f...
-
Alain.Frisch@e...
-
John Goerzen
- Henri DF
- Shawn Wagner
- james woodyatt
-
Alain.Frisch@e...
- Basile STARYNKEVITCH
-
John Goerzen
- Kenneth Knowles
- Florian Hars
-
Maxence Guesdon
- Eric C. Cooper
-
Kenneth Knowles
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Jacques GARRIGUE <garrigue@k...> |
| Subject: | [Caml-list] Re: Proposal: community standard library project |
From: Benjamin Geer <ben@socialtools.net> > I'm envisaging a new 'community standard library' project which would > supplement (and perhaps partly replace) INRIA's standard library, and in > which: > > * Libraries would be categorised according to function, e.g. > data structures, Unicode, I/O, network protocols, etc. > > * No duplicate or incompatible functionality would be allowed > in each functional area. People would have to cooperate > to make their stuff work together. > > * Minimum standards of portability, documentation, etc. would be > checked. > > * Everything would be released via GODI. Writing down this makes clearer part of the problem with ocaml and/or its community: your second point would be very hard to satisfy. Why? Because ocaml gives you many ways to define an API for any functionality. And does not try to decide which is better. So you can only end up with duplicate libraries, according to personal tastes. Not only there are plenty of duplicate libraries around, but I'm sure that many ocaml programmers prefer to create their own private library rather than using some available one. You can be functional or imperative, use optional arguments or not, use objects or modules, etc... Even interfacing a C library can be done in many different ways... This does not mean that people should not cooperate, just that you cannot force them to. The 1st point is reasonable. This is already what the humps are doing, but a system allowing requests for new functionalities would be nice too. The 3rd point, I would rather see it as having more meta-documentation, ie information on libraries without having to download and install: requirements, extensiveness, quality of the documentation, user reviews... The last point is clear enough. Jacques Garrigue ------------------- 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