From: "Warp" <warplayer@free.fr>
To: "Tom Hirschowitz" <Tom.Hirschowitz@inria.fr>,
"OCaml" <caml-list@inria.fr>
Subject: Re: [Caml-list] Modules Order
Date: Thu, 18 Apr 2002 16:41:33 +0200 [thread overview]
Message-ID: <004201c1e6e7$2300e6a0$3900a8c0@warp> (raw)
In-Reply-To: <15550.55633.886446.494339@paille.inria.fr>
> Does this seem reasonable?
>
> Only put a link in the graph when the dependency is dynamic
> (ie not on types), and build all the cmi files first, so
> that they are available when compiling to cmos.
> Just crash when this graph has a cycle.
>
> I think it's not that difficult, because I did something
> similar for a prototype type-checker for my mixins.
>
> But this supposes to change the way Makefiles are built I guess.
>
> What are your plans about that?
The problem here is that we don't know if we're using either only types or
functions from the other module.
The purpose of that is to enable automatic compilation of one project
composed of many files.
Nicolas Cannasse
-------------------
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:[~2002-04-18 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 14:01 Warp
2002-04-18 14:24 ` Christian Lindig
2002-04-18 14:31 ` Michal Moskal
2002-04-18 14:40 ` Christian Lindig
2002-04-18 14:45 ` Michal Moskal
[not found] ` <15550.55633.886446.494339@paille.inria.fr>
2002-04-18 14:41 ` Warp [this message]
2002-04-18 20:55 ` John Max Skaller
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='004201c1e6e7$2300e6a0$3900a8c0@warp' \
--to=warplayer@free.fr \
--cc=Tom.Hirschowitz@inria.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;
as well as URLs for NNTP newsgroup(s).