caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Matej Košík" <5764c029b688c1c0d24a2e97cd764f@gmail.com>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] a question about "ocamlopt" and "ocamldep"
Date: Wed, 14 Mar 2012 12:38:43 +0000	[thread overview]
Message-ID: <4F609153.5040000@gmail.com> (raw)
In-Reply-To: <CAPFanBG24dwykhjUegS-af7qQ+1HAaryxVYmvVkjoqrNhF+A5g@mail.gmail.com>

On 03/14/2012 11:23 AM, Gabriel Scherer wrote:
>> :-(
> 
> I don't understand. Why is it sad to have the *ability* to perform
> cross-module implementation-dependent optimizations (at the inevitable
> cost of locally damaging separate compilation) *if* you wish?

There are two scenarios when I use the compiler:

Scenario 1 (most frequent): when I want to incrementally remove typing
errors during development. Various optimizations do not matter here.
What matters is a short time to rebuild everything (that has to be rebuilt).

Scenario 2 (rare one): to produce the final product
where quality of various optimizations matter more than
the amount of required compilation time

If dropping dependencies of *.cmx files on other *.cmx files (rather
than on *.cmi files) requires manual intervention or careful thinking,
then ocamlopt, with this behavior, is not ideal tool for Scenario 1
(while still being perfectly suitable for Scenario 2).

  reply	other threads:[~2012-03-14 12:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 10:31 Matej Košík
2012-03-14 11:23 ` Gabriel Scherer
2012-03-14 12:38   ` Matej Košík [this message]
2012-03-14 13:19     ` Virgile Prevosto
2012-03-14 17:12       ` Gabriel Scherer
  -- strict thread matches above, loose matches on Subject: below --
2012-03-13 18:19 Matej Košík
2012-03-13 18:34 ` Matthias Puech
2012-03-13 19:26   ` Gabriel Scherer

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=4F609153.5040000@gmail.com \
    --to=5764c029b688c1c0d24a2e97cd764f@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=gabriel.scherer@gmail.com \
    /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).