caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Joel Reymont <joelr1@gmail.com>
To: Andreas Rossberg <rossberg@mpi-sws.org>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Re: module typing issue
Date: Fri, 25 Mar 2011 15:57:53 +0000	[thread overview]
Message-ID: <87204922-C93B-492A-BDE3-98707F8B30AF@gmail.com> (raw)
In-Reply-To: <63968844-AD95-4359-80F0-E9E071CF6518@mpi-sws.org>


On Mar 25, 2011, at 3:46 PM, Andreas Rossberg wrote:

> I don't think it ever makes sense to define private type abbreviations in a structure - they are intended for use in signatures. Just drop the private from your example.

This compiles but fails as soon as I try to replace dispatch in MyReply (bottom) with 

  let dispatch = function | A -> 1

This is obvious conceptually as MyReply doesn't know about the variant type defined in MyRequest. 

How do I make let MyReply know about it?

	Thanks, Joel

--- x.ml

module type Message = 
sig 
 type obj 
 type variant
 val make : unit -> obj
 (* encapsulate object in a variant type *)
 val convert : obj -> variant
 val print : obj -> unit
end

module type Request = 
sig 
 include Message
end

(* dispatches based on a request *)

module type Reply = functor (Req : Request) ->
sig 
 include Message
 val dispatch : Req.variant -> obj
end

module Server (Req : Request) (REP : Reply) =
struct 
 module Rep = REP(Req)
 let server = 
   while true do
     let req = Req.make () in
     let var = Req.convert req in
     let rep = Rep.dispatch var in
     Req.print req;
     Rep.print rep
   done
end

module MyRequest : Request =
struct
 type obj = int
 type variant = A
 let make () = 1
 let convert o = A
 let print o = ()
end

module MyReply : Reply = functor (Req: Request) ->
struct
 type obj = int
 type variant = B
 let make () = 2
 let convert o = B
 let print o = ()
 let dispatch _ = 2
end

module MyServer = Server (MyRequest) (MyReply)


--------------------------------------------------------------------------
- for hire: mac osx device driver ninja, kernel extensions and usb drivers
---------------------+------------+---------------------------------------
http://wagerlabs.com | @wagerlabs | http://www.linkedin.com/in/joelreymont
---------------------+------------+---------------------------------------





  reply	other threads:[~2011-03-25 15:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25  8:34 [Caml-list] " Joel Reymont
2011-03-25  8:44 ` [Caml-list] " Joel Reymont
2011-03-25 14:17   ` Joel Reymont
2011-03-25 15:46     ` Andreas Rossberg
2011-03-25 15:57       ` Joel Reymont [this message]
2011-03-25 16:04         ` Andreas Rossberg
2011-03-25 16:42       ` Guillaume Yziquel
2011-03-25 16:59         ` Andreas Rossberg
2011-03-25 19:01           ` Guillaume Yziquel
2011-03-25 19:13             ` Andreas Rossberg
2011-03-28  7:53             ` Alain Frisch
2011-03-28 10:33               ` Guillaume Yziquel
2011-03-28 11:29                 ` David Allsopp
2011-03-28 11:58                   ` Guillaume Yziquel
2011-03-28 12:11                     ` David Allsopp
2011-03-28 12:29                       ` Guillaume Yziquel
2011-03-28 12:23                     ` Alain Frisch
2011-03-28 12:39                       ` Guillaume Yziquel
2011-03-28 11:32               ` David Allsopp
2011-03-28 12:02                 ` Guillaume Yziquel

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=87204922-C93B-492A-BDE3-98707F8B30AF@gmail.com \
    --to=joelr1@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=rossberg@mpi-sws.org \
    /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).