Browse thread
Re: Yet another question about the module system
- Jocelyn Serot
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Jocelyn Serot <jserot@e...> |
| Subject: | Re: Yet another question about the module system |
Ok, i had my both thoughts cleared (thanks to you) and my pb solved (thanks to F. Rouaix). The solution seems to write an explicit module type in the first file : ******* file bar.ml ********** module type BAR = sig type t val x : t end ****************************** and to refer to this signature in the second file: ******* file foo.mli ********* open Bar module type FOO = sig type t type p val y : t end module Make(B:BAR) : (FOO with type t = B.t) ****************************** Thanks for your help. Oh, and "pendant que j'y suis" as we say in french :-) i have another question: Is there a way to tell the ocamlopt native compiler to use a given C compiler after it has been built and installed ? If not, what is the configuration option to modify in order to specify such a C compiler (which may be distinct from the compiler used for building the caml tools) ? Jocelyn Serot -- E-mail: jserot@epcc.ed.ac.uk (->29/11) ...................................... S-mail: LASMEA - URA 1793 CNRS, Universite Blaise Pascal, 63177 Aubiere cedex Tel: (33) 73.40.73.30 - Fax: (33) 73.40.72.62 ............................... .... http://wwwlasmea.univ-bpclermont.fr/Personnel/Jocelyn.Serot/Welcome.html