> From owner-caml-list@pauillac.inria.fr Wed Jun 13 19:09:47 2001
> From: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
> To: wester@ilt.fhg.de
> Cc: caml-list@inria.fr
> X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f
> Subject: Re: [Caml-list] Natively compiled code and toplevel 
> Mime-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Date: Thu, 14 Jun 2001 11:06:45 +0900
> X-Dispatcher: imput version 20000228(IM140)
> 
> > I looked over the mktoplevel manual and as far as I understand  it is 
> > possible to link compiled C-code with the mktoplevel but not to link
> > with natively compiled OCaml code. Am I right and why is this the case? 
> > 
> > Rolf
> 
> You're right. To be efficient, native ocaml code does not use the same
> conventions as C, so you cannot call a natively compiled ocaml function
> as though it were a C function.
> 
> Fabrice Le Fessant has done some work on the other way round. See
> asmdynlink on this page: http://pauillac.inria.fr/~lefessan/src/.
> The idea is to be able to execute ocaml bytecode inside a native
> program. With a large amount of hacking, it should be possible to
> build an ocaml.opt, which in turn would allow you to link the toplevel
> with native code...
> I'm not sure it is worth the pain.

FWIW, Jocaml allows this and Jocaml is an extension of Ocaml.

> 
> Cheers,
> 
> Jacques Garrigue
> -------------------
> Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
> To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr
> 
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr