Browse thread
ocamlbuild and automatic dependencies
[
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: | 2007-03-17 (00:18) |
From: | skaller <skaller@u...> |
Subject: | Re: [Caml-list] ocamlbuild and automatic dependencies |
On Fri, 2007-03-16 at 15:22 +0100, Daniel de Rauglaudre wrote: > Hi, > > > On Mar 14, 2007, at 1:11 PM, Nicolas Pouillard wrote: > > > >module F = Foo > > This means : "define a module named F whose *implementation* is the > implementation of Foo". > > Therefore it is normal that at link time, the system asks for an > implementation of foo. > > IMHO, it is not a bug. No, just hard to understand without an explanation such as the one you gave which is good, thanks! So actually, this F is distinct from Foo, even though all the members are the same. In particular, if Foo has an abstract type t, is F.t the same type as Foo.t? -- John Skaller <skaller at users dot sf dot net> Felix, successor to C++: http://felix.sf.net