ocaml

I have been rewriting many OCaml standard library functions to be tail-recursive lately. Given that this has entailed straight-forward CPS transformation, I am left puzzling over why the default versions are not written this way. As an example, in the standard library, map is defined as: let rec map f = function [] -> [] | a::l -> let r = f a in r :: map f l I have rewritten it to be: let map f l = let rec aux l k = match l with [] -> k [] | a::l -> aux l (fun rest -> k (f a :: rest)) in aux l (fun x -> x) In my experience, tail recursive versions of non-trivial functions often trade space

By "concurrency" I mean lightweight processes like Erlang's actors and concurrent GC aimed to make such a processes work smoothly. It would be very cool if INRIA got rid of those drawbacks of the current OCaml implementation to make OCaml more prepared for the multicore future. P.S. F# isn't what I'm looking for. no I cannot be more concise without reproducing his explanation. It speaks for itself. Yes, this is from 2002, but I haven't heard him sway on the issue, and from the text, it doesn't seem probable at all that he would back down from these goals. For current developments on concurrent

While working on my compiler I got this error: Program received signal SIGSEGV, Segmentation fault. __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33 How do I get details of what went wrong here? I know from the backtrace it's a memcpy line that causes it, but how do I see how the memory is aligned? And how do I know how it should be aligned? The project is a compiler with an LLVM back-end using the Zend/PHP runtime with the OCaml garbage collector, so there's is a lot of things that can go wrong. I suspect this line being part of the problem: zend_string

I suddenly started to get this error. I don't know how to diagnose or fix it. Am I supposed to grep through bar.ml and check every Big_int function against signature in Big_int.mli ? File "foo.ml", line 1, characters 0-1: Error: The files /home/bar.cmi and /usr/lib/ocaml/big_int.cmi make inconsistent assumptions over interface Big_int Generally this message means that one .mli file has been recompiled recently but not the other. Since one of the .mli files is in your OCaml library, it might mean that you've upgraded your OCaml installation but haven't recompiled bar.mli since then. What

I am attempting to use the Core module in utop , as originated by Jane Street and installed using opam . Here's the problem utop # open Core.Std;; Error: Unbound module Core utop does not seem to have the path to the Core module. How do you specify a path that can be found by utop to access the Core module? Is there a utop init file that specifies library paths ? I have the same error message from the OCaml 4.01.0 interpreter. The only way I can avoid this error is actually changing directory to /Users/myname/.opam/system/lib/core . I had the same problem, the directions here got it working

In F# I can't live without pipes ( <| and |> ) let console(dashboard : Dashboard ref) = let rec eat (command : string) = command.Split(' ','(',')') |> Seq.filter(fun s -> s.Length <> 0) |> fun C -> (Seq.head C).ToUpper() |> fun head -> Can I use <| and |> in OCaml? LiKao These are available since OCaml 4.01. However, <| is named @@ there, so it has the correct operator associativity. Alternatively, you can either define them yourself: let (|>) v f = f v let (<|) f v = f v (* or: *) let (@@) f v = f v Or you use Ocaml batteries included , which has the |> and <| operators defined in BatStd. 来源：

Please consider the following code: module A = struct type r = { i : int; s: string } end module B = struct type r = { i : int; s : string } end let f (x : A.r) : B.r = match x with { i; s } -> { i = 2*i; s = "" } Two modules define exactly the same record. A function f converts an A record to a B record. The warning is already emitted during compilation, but also visible interactively. On the ocaml cli, it seems that a call to f does the intended thing: # let x = f { i = 5; s = "ab" };; Characters 10-29: let x = f { i = 5; s = "ab" };; ^^^^^^^^^^^^^^^^^^^ Warning 40: this record of type

Is anybody aware of programs for profiling OCaml code apart from using the -p option while compilation and then using gprof? I am asking this question in order to check if the sampling time of 0.01 second can be lowered further? poorman's profiler is perfectly applicable for OCaml programs. The same idea works out for profiling allocations as well. Never used it but ocamlviz is another option. You can also use ocaml-memprof, a compiler patch ( 3.12.0 and 3.12 1 ) written by Fabrice Le Fessant, that adds memory profiling features to ocaml programs. EDIT Now you have ocp-memprof , an OCaml