caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] ocamlbuild and automatic dependencies
Date: Sat, 17 Mar 2007 11:18:26 +1100	[thread overview]
Message-ID: <1174090706.10421.29.camel@rosella.wigram> (raw)
In-Reply-To: <20070316142205.GB28353@yquem.inria.fr>

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


  reply	other threads:[~2007-03-17  0:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-14 12:14 Joel Reymont
2007-03-14 12:24 ` [Caml-list] " Nicolas Pouillard
2007-03-14 12:36   ` Joel Reymont
2007-03-14 12:43     ` Nicolas Pouillard
2007-03-14 12:47       ` Joel Reymont
2007-03-14 13:11         ` Nicolas Pouillard
2007-03-14 20:11           ` skaller
2007-03-14 20:57             ` Alain Frisch
2007-03-15  3:46               ` skaller
2007-03-16 14:00           ` Joel Reymont
2007-03-16 14:22             ` Daniel de Rauglaudre
2007-03-17  0:18               ` skaller [this message]
2007-03-17  3:01                 ` Daniel de Rauglaudre
2007-03-17  8:14                 ` Alain Frisch
2007-03-17 13:52                   ` Modules for Dummies skaller
2007-03-16 14:40             ` [Caml-list] ocamlbuild and automatic dependencies Jacques Garrigue

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=1174090706.10421.29.camel@rosella.wigram \
    --to=skaller@users.sourceforge.net \
    --cc=caml-list@inria.fr \
    --cc=daniel.de_rauglaudre@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).