From: Jon Harrop <jon@jdh30.plus.com>
To: "caml users" <caml-list@inria.fr>
Subject: Re: [Caml-list] Combined compilation and linking
Date: Tue, 26 Oct 2004 21:02:39 +0100 [thread overview]
Message-ID: <200410262102.39677.jon@jdh30.plus.com> (raw)
In-Reply-To: <1098812039.2903.147.camel@pelican.wigram>
On Tuesday 26 October 2004 18:34, skaller wrote:
> Why do we need separate compilation
> and linkage in the style of C on modern systems?
In other languages you might want to do separate compilation in order to
distribute object files instead of source. Seeing as this doesn't really work
in OCaml, I can't see that another approach couldn't be equally productive.
> Surely, we would like to have fast compilations, but
> why can't the compiler treat that as an automatic
> optimisation, rather than a user managed one?
As a start, this could be performed by a combined compiler-linker which could,
for example, cache compilations by file name (module name) and the hash and
contents of the file for the "n" most recently compiled files. Then you just
feed this program all your source files.
More advanced versions could split source files up and compile each part
separately, combining the result.
A preliminary test of the potential productivity of this would be to measure
the time taken to load vs the time taken to compile some example source
files.
Cheers,
Jon.
prev parent reply other threads:[~2004-10-26 20:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 1:49 [Caml-list] Single-case union types as strong typedefs Nathaniel Gray
2004-10-23 3:31 ` Jacques Garrigue
2004-10-23 3:39 ` David Brown
2004-10-23 5:00 ` skaller
2004-10-23 21:49 ` Nathaniel Gray
2004-10-23 21:24 ` Nathaniel Gray
2004-10-23 21:33 ` Nathaniel Gray
2004-10-24 3:00 ` John Prevost
2004-10-24 5:18 ` skaller
2004-10-24 22:52 ` Nathaniel Gray
2004-10-25 13:21 ` Damien Doligez
2004-10-25 14:25 ` Jacques Carette
2004-10-26 14:07 ` Damien Doligez
2004-10-26 15:05 ` Jacques Carette
2004-10-26 17:34 ` skaller
2004-10-26 20:02 ` Jon Harrop [this message]
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=200410262102.39677.jon@jdh30.plus.com \
--to=jon@jdh30.plus.com \
--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