Re: [Ocaml-lib-devel] candidate functions

[Nicolas C. <war...@fr...>]

> >The last point is about compilation and module linkage.
> >If you want to do "open ExtLib" and then "open List" for exemple, then
> >ExtLib have to be ONE big module (perhaps several files linked together
with
> >the -pack option, but still one big cmo ) and so will always be entirely
> >linked with your bytecode if you're using only one function of it... so
> >that'll prevent us from adding new modules since each time it will get
> >bigger and bigger. If you have another structure/compilation proposal....
> >
>
> I recall the question about namespaces in the COAN thread and X. Leroy
> saying that the -pack option was still unstable... Could we ask for it
> to "drift" so that the support would be merely "namespatial" in the
> sense that no big cmo file got build out of the multiple cmo's being
> packed... Or at least that cmos generated with -pack were rather stubs
> for the modules being assembled so that they didn't have to be loaded as
> a *whole*. I'm not into compiler/linker construction so I don't know
> about the complexity of this but it doesn't look altogether unreasonable
> to me... It's for the benefit of the generated code to be lean!

I don't think this kind of hack will be done by the caml team like this.
It takes time to find a good way to do it, and might not be done for the
3.07 release.
So we cannot rely on it, and have to find our own packaging way.

Nicolas Cannasse