Browse thread
[Caml-list] Dynamically evaluating OCaml code
-
John Goerzen
- Vitaly Lugovsky
- Samuel Mimram
-
Basile Starynkevitch
-
Issac Trotts
- Dustin Sallings
-
Brian Hurt
- Oleg Trott
- Ville-Pertti Keinonen
-
John Goerzen
-
Markus Mottl
-
Richard Jones
-
Markus Mottl
- Jon Harrop
-
John Goerzen
- Jean-Marc EBER
-
Trevor Andrade
-
Gerd Stolpmann
- skaller
-
John Goerzen
-
Gerd Stolpmann
-
Christophe TROESTLER
-
Gerd Stolpmann
-
Christophe TROESTLER
- Brandon J. Van Every
- John Goerzen
- Jacques GARRIGUE
-
Christophe TROESTLER
-
Gerd Stolpmann
-
Christophe TROESTLER
- Matt Gushee
-
Gerd Stolpmann
- Benjamin Geer
-
Gerd Stolpmann
- skaller
-
Markus Mottl
- John Goerzen
- Jon Harrop
-
Richard Jones
- Fernando Alegre
- Jean-Marc EBER
- Kenneth Knowles
- Brian Hurt
- skaller
-
Markus Mottl
- Issac Trotts
- Basile Starynkevitch
-
Issac Trotts
- clement capel
- Jon Harrop
- Walid Taha
[
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: | Markus Mottl <markus@o...> |
| Subject: | Re: [Caml-list] Dynamically evaluating OCaml code |
On Thu, 08 Apr 2004, John Goerzen wrote: > Also, there is no string_of_char function (I'd have to use fill). That's not quite true: there is "String.make", which does what you want. > Similar complaints exist for working with subsets of lists; it's really > too hard to say "replace elements 4 through 9 with this", "delete > elements 4 through 9", "return elements 4 through 9", etc. Yes, it's hard to do this with the current standard library. The question is: who needs these functions anyway? I can't remember ever having felt a need for them. > (While we're at it, I think it's silly that there is a list and an > array type). I beg your pardon - what else do you have in mind??? > Yes, I could write functions to do all of this, but my point is that > I shouldn't have to. The point of the standard library is not to have a function for every imaginable problem but to have ones that cover standard problems. > This library problem hurts productivity, and in some cases makes OCaml > less productive than even C. Things are not half as bad as you describe them here. There may be cases where C is more productive - because you happen to have a library function for the problem. But even in this case you can just interface to C, which is really not that difficult. There are surely cases where the OCaml standard library lacks generally useful functionality, but it's usually good enough for most problems. Regards, Markus ------------------- 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