Maybe these links will be more useful:
http://groups.google.com/group/fa.caml/browse_thread/thread/2827ec9d553e7760/183ac101fef47132?lnk=st&q=group%3Afa.caml+author%3Axavier+loading+native&rnum=10#183ac101fef47132
http://groups.google.com/group/fa.caml/browse_thread/thread/efc434c41cc88ded/663f229e008648e0?lnk=st&q=group%3Afa.caml+author%3Axavier+binary+compatibility&rnum=4#663f229e008648e0

In the first (newer) post linked above Xavier says:

"""
Feature 3- (dynamic code loading) is already available in bytecode
through the Dynlink API.  I understand there's a demand for having it
in native-code as well, and that might be possible without too much fuss,
at least on selected operating systems.
"""

This seems to conflict with Xavier's statements earlier in this thread.  I
hope dynamic loading is still being considered, as I can't see using
OCaml for medium-to-large scale applications programming without it.
Who wants to write an app without plugins these days?

Cheers,
-n8

On 1/1/06, Ker Lutyn <ker527mail@yahoo.com> wrote:
> <http://groups.google.com/groups?q=group:fa.caml+author:xavier+loading+native>
>
> --- David Fox <david.fox@linspire.com> wrote:
>
> > Xavier Leroy wrote:
> >
> > >Dynamic loading of OCaml code from OCaml code raises many other
> > >issues.  It is currently supported for bytecode only, and will not be
> > >available for native code in the forseeable future.  I have already
> > >discussed this on this list earlier.
> > >
> > >
> > I can seem to locate this discussion - do you remember any keywords I
> > might search for?
> >

--
>>>-- Nathaniel Gray -- Caltech Computer Science ------>
>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->