From: Richard Jones <rich@annexia.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Syntactic inclusion of a.ml in b.ml ?
Date: Sat, 9 Apr 2005 11:35:32 +0100 [thread overview]
Message-ID: <20050409103532.GA20625@furbychan.cocan.org> (raw)
In-Reply-To: <20050408174142.GA1804@galois>
On Fri, Apr 08, 2005 at 07:41:42PM +0200, Sébastien Hinderer wrote:
> (How) is it possible to include syntactically a file a.ml in a file
> b.ml ?
>
> One method that seems to w)rk is to rename b.ml to b.ml.c,
> and then have in b.ml.c a line saying
> #include "a.ml"
> And with this, gcc -E b.ml.c > b.ml
> produces a file that ocamlc can apparently handle.
I'm not 100% clear on what you want to do.
A common requirement is to split a large module into a number of
smaller files, which is then compiled back into a single large module.
This can be done using a preprocessor (such as cpp) - see the -pp
option to the compiler. Often it's better just to use a single large
file and a capable editor, with "folding"[1] capabilities.
Another one is to include the symbols from one module in another.
This can be done using the 'include' directive in OCaml, eg:
-- a.ml ----
let foo = 1
------------
-- b.ml ----
include A
let bar = 2
------------
Now, if compiled in the correct order, module B will export symbols
'foo' and 'bar'.
'include' and 'open' are very similar. The difference is that
'include' causes the symbols imported to be (re-)exported. 'open A'
on the other hand makes the symbols in A available inside B, but they
are not exported in B's interface.
Another option is to use the -pack argument when linking [not
supported on all platforms]. This causes modules to be nested inside
a "super-module".
For example,
ocamlc -pack -o c.cmo a.cmo b.cmo
(IIRC) creates a module called C containing C.A and C.B modules.
Rich.
[1] http://www.moria.de/~michael/fe/folding.html
--
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Team Notepad - intranets and extranets for business - http://team-notepad.com
next prev parent reply other threads:[~2005-04-09 10:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 17:41 Sébastien Hinderer
2005-04-09 10:35 ` Richard Jones [this message]
2005-04-09 13:20 ` Sébastien Hinderer
2005-04-09 14:45 ` [Caml-list] " Radu Grigore
2005-04-09 15:49 ` Sébastien Hinderer
2005-04-09 21:15 ` [Caml-list] " Radu Grigore
2005-04-09 17:51 ` [Caml-list] " Robert Roessler
2005-04-09 21:27 ` William D.Neumann
2005-04-10 16:53 ` Richard Jones
2005-04-09 11:55 ` Olivier Andrieu
2005-04-09 12:54 ` sejourne_kevin
2005-04-09 21:16 ` Martin Jambon
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=20050409103532.GA20625@furbychan.cocan.org \
--to=rich@annexia.org \
--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).