http://staffingpower.com/

The code should compile to someting like

for (var i$60 = 1; i$60 <= 5; i$60++) (function() { var i$60$ = i$60; a$59 = $(_f(function (x$61) { return x$61 + i$60$; }), a$59)})();

instead of

for (var i$60 = 1; i$60 <= 5; i$60++) a$59 = $(_f(function (x$61) { return x$61 + i$60; }), a$59);

Only functions, not blocks, are scopes in javascript.
The assers in Isaacs code should obviously be

assert ((a.(0) 3) == 8);
assert ((a.(1) 3) == 7);;

And print_int in ocamljs adds a newline that ocaml proper doesn’t add.

for (var i$60 = 1; i$60

let foo() =
let a = ref [] in
for i = 1 to 5 do
a := (fun x -> x + i) :: !a;
done;
Array.of_list !a;;

let foo_test() =
let a = foo() in
assert ((a.(0) 3) == 4);
assert ((a.(1) 3) == 5);;

foo_test();;

http://cadmium.x9c.fr/downloads.html

Your snippet manager would be useful in ocamljs since minimizing the resulting Javascript is important for web apps.

Did you have access to some documentation on the internals of the ocaml compiler or did you just read the source code?

In case you had access to docs, could you please tell me what you had to do to obtain it?
If you just read the source would you like to write some documents (a tutorial or a blog post or whatever you like) explaining a bit the internals of the compiler?

I’m working on a snippet manager to ease the distribution and reuse of ocaml code and to reduce the size of the binary by linking only those pieces of libraries that are used in your application and not the whole module. We already have a working prototype implementation using ocamldoc but we need to access the internals of the compiler to get a better tool. Our snippet manager will be released as free software.
If you are interested I can provide you further details.

When you get a bunch of functional programmers in a room, and leave them with nothing else to do, they’ll widdle away the hours working on interesting back-ends for their favorite compilers, like the OCaml to Javascript compiler. Yes, you really did …