From: Damien Doligez <Damien.Doligez@inria.fr>
To: caml-list@inria.fr
Subject: Re: automatic construction of mli files
Date: Wed, 26 Jul 2000 14:58:27 +0200 [thread overview]
Message-ID: <200007261258.OAA10269@tobago.inria.fr> (raw)
>From: Jean-Christophe Filliatre <filliatr@csl.sri.com>
>In the extreme situation where there is no real need for writing an
>interface, you can either simply not write one (this is not mandatory)
>or generate it from the code with "ocamlc -c -i".
There are two technical details you should all know concerning .mli
files:
1. If you don't use .mli files, or if you generate them automatically
from the corresponding .ml files, then you lose separate
compilation: whenever you change a semicolon in foo.ml, all
the files that depend on module Foo will have to be recompiled.
This may or may not be a big problem depending on the size of your
project.
2. Due to rather complex implementation issues, if you don't use .mli
files and let the compiler generate the .cmi from the .ml, then
garbage collection will be slightly slower. If you do it for all
your files, you might lose as much as 8% on the speed of your
program.
-- Damien
next reply other threads:[~2000-07-27 17:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-26 12:58 Damien Doligez [this message]
2000-07-27 17:46 ` Francois Rouaix
-- strict thread matches above, loose matches on Subject: below --
2000-07-27 19:04 Damien Doligez
2000-07-24 5:34 Julian Assange
2000-07-24 20:48 ` Olivier Andrieu
2000-07-26 16:03 ` John Max Skaller
2000-07-24 22:02 ` Jean-Christophe Filliatre
2000-07-26 16:09 ` John Max Skaller
2000-07-24 22:09 ` John Prevost
2000-07-24 23:14 ` David Brown
2000-07-25 1:13 ` Jacques Garrigue
2000-08-01 11:22 ` Anton Moscal
2000-08-02 12:03 ` Dmitri Lomov
2000-08-02 14:13 ` Gerard Huet
2000-07-25 11:48 ` Hendrik Tews
2000-07-26 10:16 ` David Delahaye
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=200007261258.OAA10269@tobago.inria.fr \
--to=damien.doligez@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