caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Max Skaller <maxs@in.ot.com.au>
To: caml-list@inria.fr
Subject: Module naming
Date: Wed, 02 Feb 2000 12:39:11 +1100	[thread overview]
Message-ID: <38978ABF.7898BDB6@in.ot.com.au> (raw)

I'm confused: why doesn't this work? [I get unbound type ctor message]
[shortened version]

module type X = sig type one end
module type Y = sig type two end
module type XY = sig module type XX = X module type YY = Y end
module type Client = functor (T: XY) ->
  sig val f: T.XX.one -> unit end
             ^^^^^^^^

What I expected was that T.XX.one would refer to the
type X.one, but this doesn't seem to be the case.

-- 
John (Max) Skaller at OTT [Open Telecommications Ltd]
mailto:maxs@in.ot.com.au      -- at work
mailto:skaller@maxtal.com.au  -- at home




             reply	other threads:[~2000-02-02 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-02  1:39 Max Skaller [this message]
2000-02-02 17:58 ` Andreas Rossberg
2000-02-02 19:20 ` Remi VANICAT

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=38978ABF.7898BDB6@in.ot.com.au \
    --to=maxs@in.ot.com.au \
    --cc=caml-list@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).