From: Guillaume Yziquel <guillaume.yziquel@citycable.ch>
To: caml-list@inria.fr
Subject: Including code from a .cm[ox] into another .cm[ox]
Date: Thu, 12 Nov 2009 13:16:30 +0100 [thread overview]
Message-ID: <4AFBFC9E.8010802@citycable.ch> (raw)
Hello.
Imagine I have a file named a.ml containing
> module C = struct
> include B
> end
and a file named b.ml containing the code
> let f x = x + 1
When I compile everything to .cmo files, I cannot load a.cmo from the
toplevel without loading b.cmo beforehand.
Is there a way to make the 'include B' statement to include the code of
the B module in the C submodule directly so that it is not required to
load the b.cmo file before loading the a.cmo file?
That would be extremely useful to me...
All the best,
--
Guillaume Yziquel
http://yziquel.homelinux.org/
next reply other threads:[~2009-11-12 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 12:16 Guillaume Yziquel [this message]
2009-11-12 12:41 ` [Caml-list] " Philippe Veber
[not found] ` <721f7f5a0911120441h7706cd02ud9b6b993532b88f5@mail.gmail.com>
[not found] ` <4AFC0515.5050306@citycable.ch>
2009-11-12 13:35 ` Philippe Veber
2009-11-12 14:16 ` 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=4AFBFC9E.8010802@citycable.ch \
--to=guillaume.yziquel@citycable.ch \
--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).