From: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
To: Julien.Signoles@lri.fr
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] extensible records again
Date: Wed, 24 Mar 2004 19:04:44 +0900 [thread overview]
Message-ID: <20040324190444P.garrigue@kurims.kyoto-u.ac.jp> (raw)
In-Reply-To: <Pine.LNX.4.43.0403240924110.28297-100000@pc8-119.lri.fr>
From: Julien Signoles <Julien.Signoles@lri.fr>
> I think you don't use t0 in Y0 and Ysig because t0 is enclosed
> in XY. I would write somethink like:
>
> (* [...] *)
> module Y0(Xrec : Xrec) = struct
> module XY = X0(Xrec)
> type t = [XY.t | `C]
> end
> module type Ysig = sig
> module XY : Xsig
> type t = [ XY.t | `C]
> end
> module rec Y : (Ysig with module XY = X0(Y)) = Y0(Y)
Nicer. I didn't know that you could specify modules inside a signature
through functor application. Looks powerful.
This allows this even more modular encoding:
open Printf
module type Xt = sig type t end
module type Xrec = sig module T : Xt val show : T.t -> string end
module X0t (Xt : Xt) = struct type t = [`A of Xt.t | `B] end
module X0(Xrec : Xrec) =
struct
module T = X0t(Xrec.T)
let rec show = function
`A x -> "A" ^ Xrec.show x
| `B -> "B"
end
module rec X : (Xrec with module T = X0t(X.T)) = X0(X)
module Y0t(Xt : Xt) = struct type t = [X0t(Xt).t | `C] end
module Y0(Xrec : Xrec) =
struct
module T = Y0t(Xrec.T)
module XY = X0(Xrec)
let rec show = function
#XY.T.t as x -> XY.show x
| `C -> "C"
end
module rec Y : (Xrec with module T = Y0t(Y.T)) = Y0(Y)
Note of course that this is not very interesting on this simple
example. Using that many modules only gets useful if you have several
mutually recursive types.
Jacques Garrigue
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-03-24 10:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-21 6:21 Michael Vanier
2004-03-21 8:08 ` Oleg Trott
2004-03-21 8:40 ` Michael Vanier
2004-03-21 16:10 ` Oleg Trott
2004-03-21 17:06 ` skaller
2004-03-21 17:36 ` Oleg Trott
2004-03-22 3:19 ` skaller
2004-03-22 7:49 ` Ville-Pertti Keinonen
2004-03-22 9:32 ` Oleg Trott
2004-03-22 10:25 ` Ville-Pertti Keinonen
2004-03-21 22:35 ` Michael Vanier
2004-03-22 3:39 ` skaller
2004-03-21 22:34 ` Michael Vanier
2004-03-22 3:31 ` skaller
2004-03-22 5:54 ` Michael Vanier
2004-03-23 19:14 ` skaller
2004-03-24 1:41 ` Jacques Garrigue
2004-03-24 8:44 ` Julien Signoles
2004-03-24 10:04 ` Jacques Garrigue [this message]
2004-03-21 8:53 ` Martin Jambon
2004-03-21 9:22 ` Michael Vanier
2004-03-21 17:00 ` skaller
2004-03-22 8:13 ` Achim Blumensath
2004-03-23 2:14 ` Michael Vanier
2004-03-23 7:25 ` Achim Blumensath
2004-03-31 10:05 ` Marcin 'Qrczak' Kowalczyk
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=20040324190444P.garrigue@kurims.kyoto-u.ac.jp \
--to=garrigue@kurims.kyoto-u.ac.jp \
--cc=Julien.Signoles@lri.fr \
--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