Oh.. I thought that this was going to be an actual version of Ocaml that was practical in the real world, rather than a book.
So what's impractical about Ocaml? I just looked at it and it looks cool, but I haven't tried it for anything. If they actually have event driven programming that seems like a big step over most functional languages, where I/O is kind of an afterthought. Steve Yegge wrote some points about Ocaml quite awhile ago. http://sites.google.com/site/steveyegge2/ocaml He says it is quite fast and I've seen that in other place…
My biggest complaints:
* Poor libraries - This is getting better, but it used to be a real pain to do stuff like make an HTTP request, parse JSON or XML, or connect to a database. They definitely weren't in the stdlib, and it was even pretty hard to find good third party libraries for it.
* Awkward library interfaces - Even the libraries that are included are awkward to use, like the Set and Map.
* Poor documentation - There's nothing (or was nothing) like http://perldoc.perl.org/ or http://docs.python.org/
And, off-hand, one language nitpick:
* Poorly handled strong typing - For example '+' is used to add integers while '+.' is used to add floats. The underlying reason makes sense, but there's awkward stuff like that all over. Haskell handles it better, IMO.