Date: Wed, 17 Sep 1997 17:52:59 +0100
Message-Id: <11948.199709171652@jupiter>
From: William Chesters <williamc@dai.ed.ac.uk>
To: caml-list@inria.fr
Subject: Re: ocaml: demand-driven compilation?
In-Reply-To: <199709161536.IAA10793@kronstadt.rahul.net>
<199709161536.IAA10793@kronstadt.rahul.net>
Ian T Zimmerman writes:
> Yes, it would definitely be possible to beef up ocamldep. The result
> would be a reimplementation of make in ocaml. Why reinvent the wheel?
> And why do you dislike makefiles anyways? They are the right tool for
> the job.
There are three things to know in building an executable: what modules
are needed; are they up to date; what commands are needed to
compile/link them?
`make' addresses the second (trivial) point and provides a framework
for going *some* way to help with the third. You have to bridge the
remaining gap yourself. In ocaml (as in Java) this means duplicating
information: the compiler has already used your sources to find out
what modules are needed. Furthermore the task of inferring what ocaml
and native libraries were needed for the link is easy for the
compiler, but a bit annoying for me.
That's why I dislike makefiles. make comes in at the wrong level, or
at least, at a level which was only ever right because C had no module
system worth the name.
This archive was generated by hypermail 2b29 : Sun Jan 02 2000 - 11:58:12 MET