Version française
Home     About     Download     Resources     Contact us    
Browse thread
[Caml-list] The Bytecode Interpreter...
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Jonathan Roewen <jonathan.roewen@g...>
Subject: Re: [Caml-list] The Bytecode Interpreter...
> When one #loads within a toploop, more or less the same happens.
> However, the toploop is a full compiler, and does not only have the
> symbol table, but also the current environment, i.e. the set of
> currently visible types and values with the still-needed parts of their
> definitions. As far as I know, #load does not modify the environment
> (because nothing changes - the loaded modules are already in scope when
> the .cmi file is in the search path).

Yes, but the bytecode itself is not in the environment, or at least
not initialised, hence why you need the #load right? Try using Str
module for instance. Symbols in memory, but that's it.

Anyways, my next question is: does the toplevel need dlopen & friends?
I know dynlink module would, as you stated, it performs relocation and
all that other stuff.

Jonathan