From: "Damien Guichard" <alphablock@orange.fr>
To: "caml-list@yquem.inria.fr" <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Linking mutually dependent modules for fun
Date: Fri, 16 Oct 2009 18:41:34 +0200 [thread overview]
Message-ID: <200910161841331259870@orange.fr> (raw)
In-Reply-To: <4AD33F66.4020200@wp.pl>
[-- Attachment #1: Type: text/plain, Size: 2163 bytes --]
Hi Dawid,
Have you ever considered recursive modules ?
http://caml.inria.fr/pub/docs/manual-ocaml/manual021.html#toc75
- damien
En réponse au message
de : Dawid Toton
du : 2009-10-16 09:51:57
À : caml-list@yquem.inria.fr
CC :
Sujet : [Caml-list] Linking mutually dependent modules for fun
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:
http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
Archives: http://caml.inria.fr
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs
[-- Attachment #2: Type: text/html, Size: 6871 bytes --]
next prev parent reply other threads:[~2009-10-16 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 14:38 Dawid Toton
2009-10-16 16:41 ` Damien Guichard [this message]
2009-10-19 11:01 ` [Caml-list] " Goswin von Brederlow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200910161841331259870@orange.fr \
--to=alphablock@orange.fr \
--cc=caml-list@yquem.inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).