From: Markus Mottl <mottl@miss.wu-wien.ac.at>
To: caml-list@inria.fr (OCAML)
Subject: additions to standard library?
Date: Tue, 7 Mar 2000 16:24:00 +0100 (MET) [thread overview]
Message-ID: <200003071524.QAA12371@miss.wu-wien.ac.at> (raw)
Hello,
it sometimes happens that I need functions on abstract data types in the
standard library which are not available there, but could be considered as
"usual" operations on such data. Also some other very commonly useful
functions could be added.
I was just wondering which way would be best to propose additions to the
standard libraries - I have modified a few standard modules, which now
contain additional functionality that might be useful for others, too. Is
it a good idea to send patches against the standard library in the hope
that they might be integrated?
Some specific examples include, e.g.:
* Char: functions like is_upper, is_lower, is_alpha, is_...
* Set: functions like for_all, exists, filter (find_all), partition.
These functions are in "List", too, but actually fit perfectly
to sets.
* Stack: with function top
Currently, the only way to use "Stack" in such a way is to
pop an element and push it again...
* String: the functions explode and implode for conversions of char
lists to strings and vice versa.
Especially useful for teaching, because it allows students to
use a functional style of programming when implementing string
algorithms.
There are some other additions, too, which I haven't yet fully integrated
into standard library modules.
Other people surely also have proposals for further additions to the
libraries. I can imagine that the OCaml-development team does not have the
time to deal with all such suggestions.
What do you think about the idea to make use of the "usercontrib"
CVS-repository at INRIA for such purposes? We could open a "stable" and
"development" branch for standard libraries (and "otherlibs") there, where
people could place and "peer review" their contributions. From time to
time, the OCaml-team can peek at the additions and take what they consider
useful.
This approach might be appealing to both sides:
* the OCaml-team can decide when to integrate what and won't get a bad
conscience by having to "bin" user suggestions. Additionally, some
"boring" development work can be delegated to the user community (I
know that developing compilers is more interesting than writing
standard libraries... ;-)
* the user community finally has a means to express their wishes in a
more direct way - which might increase the probability that suggestions
really get considered.
What do the developers and other users think of this idea?
Best regards,
Markus Mottl
--
Markus Mottl, mottl@miss.wu-wien.ac.at, http://miss.wu-wien.ac.at/~mottl
next reply other threads:[~2000-03-08 18:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-07 15:24 Markus Mottl [this message]
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
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=200003071524.QAA12371@miss.wu-wien.ac.at \
--to=mottl@miss.wu-wien.ac.at \
--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