I often get into trouble of cyclic dependencies when writing in OCaml.
Perhaps, I'm still not enough mentally shifted from poor languages (for
which circular design is quite natural).
Of course OCaml has many tools to deal with this: functors (which, once
introduced, spread like a disease), type variables and generalization
(which sometimes deadly collide with the functorial way) and ugly global
ref cells (which smell).
Why not try some Pascal style then? ;)
The following is what I got when studying OCaml's linking issues:
A.mli: val flip : unit - > unit
A.ml: let flip () = print_string "1"; B.flop () let _ = flip ()
B.mli: val flop : unit - > unit
B.ml: let flop () = print_string "0"; A.flip ()
C.ml: let _ = print_endline "C"
Compile:
ocamlopt -c -S A.ml
ocamlopt -c -S B.ml
The resulting .o depends on existing cmx files, so we can reach fixpoint
by doing it once more:
ocamlopt -c -S A.ml
The new compiled A happens to work with uinitialized B.
Then use some helper module:
ocamlopt -c -S C.ml
ocamlopt -dstartup -ccopt --verbose C.cmx
Modify a.startup.s to call camlA_entry instead of camlC__entry.
as -o startup.o a.out.startup.s
Verbose gcc invocation gave us proper linking command.
Replace
...std_exit.o C.o /...../stdlib.a ...
with just
...std_exit.o A.o B.o /...../stdlib.a ...
And go!
OK, I must admit that I don't know how to get startup code that would
work in general. This one had wrong memory maps and no initialization of
B... anyway it works. :)
Dawid
_______________________________________________
Caml-list mailing list. Subscription management: