Version française
Home     About     Download     Resources     Contact us    
Browse thread
[Caml-list] Hidden .cmo conflict?
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Christophe TROESTLER <Christophe.Troestler@u...>
Subject: [Caml-list] Hidden .cmo conflict?
Hi everybody,

Let us imagine I build two libs A and B.  Say that each lib is
implemented respectively by a a.ml and a b.ml file togeter with
utility fonctions splitted into a u.ml file.  This u.ml file is
different for A and B. I.e.,

   a.cma  <--  a.cmo u.cmo
   b.cma  <--  b.cmo u.cmo

The two u are different and not exported in a.cmi or b.cmi.  If then I
compile a program, say p.ml, which needs both libs A and B :

   ocamlc -o p.exe a.cma b.cma p.ml

I have no problem.  But if I have the bad idea of splitting again
utilities functions for p.ml into a u.ml file, I will get a
"...inconsistent assumptions over interface...", right?  Is there a
solution to this problem (which could really be puzzling because A and
B might have been written by somebody else and I may not know about
their "u" as it is not exported)? Can one really hide a .cmo one does
not export in the .mli?

ChriS

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners