Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
RE: [Caml-list] choosing modules at runtime
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Dave Mason <dmason@s...>
Subject: Re: [Caml-list] choosing modules at runtime
>>>>> On Wed, 02 Oct 2002 15:04:48 +0200, Alessandro Baretta <> said:

> One example: I'd love to write a generic client application capable
> of connecting with a database server for the data and to a remote
> repository of compiled modules implementing the logic of different
> application tasks the customer wishes the system to
> automate. Dynlink already partially solves the problem by allowing
> dynamic linking of cmo's over NFS, but dynamic linking over other
> network transport protocols would be a real pain, requiring explicit
> downloading and temporary storage.

We will very shortly be releasing just such a thing, called InetApp.
It only runs bytecode, but it runs transparently on Windows, Mac, and
Linux.  Hopefully the release will be in the next few weeks.

> And finally, a mixed byte-native runtime is not supported.

This is definitely something I'd like to see.  As I understand it,
there are 2 problems: bytecode vs. native function dispatch, and GC.
Trying to resolve this is on my list of things to do, but it's a long
list, so I'd love to hear that someone else has done it first!

To unsubscribe, mail Archives:
Bug reports: FAQ:
Beginner's list: