marekjm
commented
8 years ago Foreign functions receive pointers to:
- call frame,
- their static register set,
- global register set of the process,
- their calling process,
- virtual machine's CPU,
That is pretty much everything a foreign function needs; it makes it possible to load modules, call Viua code from C++ (needs testing), sending messages, receiving messages, spawning processes etc.
Closing the issue.
Current FFI is too limited. Foreign functions must receive information about what process called them, and the pointer to the environment they are running in. Once foreign functions can look around themselves more functionality can be implemented as modules, or functions, not as machine instructions.