[Vm-dev] Stupidifying FFI/library loading mechanism
Igor Stasenko
siguctua at gmail.com
Thu May 26 21:37:13 UTC 2011
On 26 May 2011 20:41, Denis Kudriashov <dionisiydk at gmail.com> wrote:
>
> Hello
>
> 2011/5/26 Igor Stasenko <siguctua at gmail.com>
>>
>> loadInternalModule: moduleName
>> loadExternalModule: moduleName path: pathToModuleLibrary
>>
>> and by analogy, for FFI:
>>
>> loadExternalLibrary: pathToExternalLibrary
>>
>
> Can you explain what the difference between this kind of module loading. Why not enough just loadLibrary: pathToLibrary?
>
If you loading VM plugin, is expects that dynamic library has
setInterpreter() function to initialize it.
Otherwise it reports failure. Then VM calls this function and if
function returns "ok" , then module is
registered in module list and you can start using primitives provided by it.
With FFI its different: an external library can hold (or not)
anything. There is no any conventions.
--
Best regards,
Igor Stasenko AKA sig.
More information about the Vm-dev
mailing list