Alessandro Baretta wrote:

> Dynamic loading? Hmmm... What about the Dynlink library? Is that not 
> what you are talking about? 

Yes, but it is bytecode. I want native code dynamic loading.
I never use bytecode.

Example: I want to build an extensible lexer. I can produce the Ocaml code
I want, but I can't compile it into a shared library which I can dlopen
and get the lex function out of.  So I have to generate C, including
the action functions :-(

I had the same problem with Vyper. I had to compile the whole
standard Python library (binary support parts) into the interpreter.
Very non-modular. By nature, all Python C modules have a
uniform interface, it would have been nice to be able to mimick
the Python technology and build the C support components
as dynamically loadable Ocaml.

-- 
John Max Skaller, mailto:skaller@ozemail.com.au
snail:10/1 Toxteth Rd, Glebe, NSW 2037, Australia.
voice:61-2-9660-0850




-------------------
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/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners