caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Petter A. Urkedal" <paurkedal@gmail.com>
To: "Soegtrop, Michael" <michael.soegtrop@intel.com>
Cc: Gabriel Scherer <gabriel.scherer@gmail.com>,
	"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] ocambuild vs ocamldep circular dependencies
Date: Sat, 9 Jul 2016 18:16:03 +0200	[thread overview]
Message-ID: <CALa9pHSj26Xe4tHnbq0u+=EuT23-yZURiFzD4No=XiMj6oG8Wg@mail.gmail.com> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A172CF20547@IRSMSX102.ger.corp.intel.com>

There is a way to do it if I understood the problem right by
functorizing and linking explicitly with the `module rec` construct:

$ cat first_sig.mli
module type S = sig
  type a
  type b
  val null : unit -> a
  val succ : b -> a
end

$ cat second_sig.mli
module type S = sig
  type a
  type b
  val null : b
  val succ : a -> b
end

$ cat first.ml
module Make (X : Second_sig.S) = struct
  type b = X.b
  type a = N | B of b
  let null () = N
  let succ x = B x
end

$ cat second.ml
module Make (X : First_sig.S) = struct
  type a = X.a
  type b = N | A of a
  let null = N
  let succ x = A x
end

$ cat both.ml
module rec A : First_sig.S with type b = B.b = First.Make (B)
       and B : Second_sig.S with type a = A.a = Second.Make (A)

There are typically some shared types at the top of the signatures,
which could be put into a separate file and included.


On 9 July 2016 at 17:16, Soegtrop, Michael <michael.soegtrop@intel.com> wrote:
> Dear Gabriel,
>
>
>
> The current implementation happens to allow them, but this does not mean
> that they are "valid programs".
>
> I see what you mean: since I can’t put both modules into a single file
> without changing the two let into let rec / and or using recursive modules,
> it is not valid OCaml, although the compiler accepts it if presented
> separately.
>
>
>
> Let me see what I can do here. The mutual dependent part is a large part of
> both modules so it wouldn’t be very nice to put them into one file. But if
> it is the only option to get a valid OCaml program, I will look into it.
>
>
>
> Still I think it is unfortunate that OCaml doesn’t support this. It makes it
> harder to structure software in an aspect oriented way. For simple data
> structures it is fine to bundle all aspects into a single module or file.
> For a data structure like a C AST, the module / file will get quite large. I
> can separate off the statements easily, but this is only a small part of the
> AST. The largest part are expressions and types, and these are recursively
> dependent on each other.
>
>
>
> Best regards,
>
>
>
> Michael
>
> Intel Deutschland GmbH
> Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
> Tel: +49 89 99 8853-0, www.intel.de
> Managing Directors: Christin Eisenschmid, Christian Lamprechter
> Chairperson of the Supervisory Board: Nicole Lau
> Registered Office: Munich
> Commercial Register: Amtsgericht Muenchen HRB 186928

  reply	other threads:[~2016-07-09 16:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-09 12:53 Soegtrop, Michael
2016-07-09 13:45 ` Gabriel Scherer
2016-07-09 15:16   ` Soegtrop, Michael
2016-07-09 16:16     ` Petter A. Urkedal [this message]
2016-07-09 20:09       ` Jonathan Protzenko
2016-07-11  7:59         ` Soegtrop, Michael
2016-07-11 15:32           ` Soegtrop, Michael
2016-07-11 15:56             ` Fabrice Le Fessant
2016-07-12  8:33   ` Goswin von Brederlow

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='CALa9pHSj26Xe4tHnbq0u+=EuT23-yZURiFzD4No=XiMj6oG8Wg@mail.gmail.com' \
    --to=paurkedal@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=gabriel.scherer@gmail.com \
    --cc=michael.soegtrop@intel.com \
    /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).