Message-Id: <5031.199610211444@tufa.epcc.ed.ac.uk>
Subject: Re: Yet another question about the module system
To: Xavier.Leroy@inria.fr (Xavier Leroy)
Date: Mon, 21 Oct 1996 15:44:25 +0100 (BST)
From: Jocelyn Serot <jserot@epcc.ed.ac.uk>
In-Reply-To: <199610211419.QAA11605@pauillac.inria.fr> from "Xavier Leroy" at Oct 21, 96 04:19:18 pm
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