On 3/7/07, Jakob Lichtenberg <jakobl@windows.microsoft.com> 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?

I'd say cross-module inlining of code ?

This happens because ocamlopt finds the base.cmx file during the
compilation of consumer. If you put your base module in a library and
remove the .cmx file, consumer won't depend on the implementation of
base, only on its interface.

-- 
  Olivier