caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: malc <av1474@comtv.ru>
To: Alain Frisch <Alain.Frisch@inria.fr>
Cc: Jakob Lichtenberg <jakobl@windows.microsoft.com>,
	caml-list@inria.fr, Donn Terry <donnte@windows.microsoft.com>
Subject: Re: [Caml-list] Dependencies and rebuilding
Date: Thu, 8 Mar 2007 19:55:06 +0300 (MSK)	[thread overview]
Message-ID: <Pine.LNX.4.64.0703081952590.2262@linmac.oyster.ru> (raw)
In-Reply-To: <45EFB59F.2080902@inria.fr>

On Thu, 8 Mar 2007, Alain Frisch wrote:

> Jakob Lichtenberg wrote:
>> If I change the body of functions in a base library, but not the
>> externally visible signature, I still have to recompile the consumers of
>> the base library prior to linking the main application.  While this is
>> not a problem in the trivial case I'll show beneath, it may be a concern
>> from a componentization and scalability point of view.  Regular C code
>> does not have this limitation.  This e-mail to request why the design is
>> as it is?
>
> A .cmx file basically contains information:
> - for the linker, most importantly dependencies information (md5 of .cmi
> and .cmx used to compile them);
> - for the compilation of other units which refer to this unit:
> cross-module optimization information (linker symbols for direct
> function calls, inlining).

That's not all, there's also information embedded to make direct calling
possible: http://groups.google.com/group/fa.caml/msg/52264cef8f6da97f

[..snip..]

-- 
vale


  reply	other threads:[~2007-03-08 16:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-07 20:07 Jakob Lichtenberg
2007-03-07 21:24 ` [Caml-list] " Olivier Andrieu
2007-03-07 21:47   ` Jakob Lichtenberg
2007-03-07 21:25 ` Zheng Li
2007-03-08  7:05 ` [Caml-list] " Alain Frisch
2007-03-08 16:55   ` malc [this message]
2007-03-09  8:01     ` Alain Frisch
2007-03-09  8:06       ` malc

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=Pine.LNX.4.64.0703081952590.2262@linmac.oyster.ru \
    --to=av1474@comtv.ru \
    --cc=Alain.Frisch@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=donnte@windows.microsoft.com \
    --cc=jakobl@windows.microsoft.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).