Eugene Chernyshov a écrit : > Hi >> You'll get back an Neko AST, which needs to be compiled into Bytecode >> instructions, then written into a .n , either on disk or in memory. >> Console.nml does just that : >> >> - read some lines until one ends with "!" >> - parse >> - compile >> - write bytecode in memory (string) >> - use the load module API (Reflex in NML) to load the module from memory >> >> Best, >> Nicolas > Done that. > > ................. > > I've found a terrible bug in your sources. loadmodule function trying to > load modules not in dll-host directory, but juct in CWD. > > Imagine that we have exe file with Neko embedded, and trying to execute > this exe file with argument of custom positioned data file's name.
This is actually not the case, or I couldn't reproduce it with a simple example. Nicolas -- Neko : One VM to run them all (http://nekovm.org)
