Matej Gagyi wrote:
Hi everybody!
At the first place, let me introduce myself: See the PS!
I'm new to the word 'Neko', but I'm impressed by what I already read.
What I did not understood maybe right is published on wikipedia:
... Since Neko is dynamically typed with no fixed classes, a developer only has to
find the proper runtime mapping (as opposed to > type mapping) so that code
executes correctly. ...
You know that text, I suppose - so does it mean that you have to have
a pre-written (and pre-build) runtime-library written specially for
Neko? Because there is maybe a way how to use runtimes of some of
languages without any porting to any other language (for example: Java
runtime - This runtime could run inside the JavaVM and the runtime
library code would be called using JNI from NekoVM).
...
I understand the quote as meaning you do not have to worry about types,
so it makes it easier to write Neko code. I believe the "runtime
mapping" is talking about mapping _at_ runtime, rather than mapping the
runtime.
Could be wrong, though.
-Justin
--
Neko : One VM to run them all
(http://nekovm.org)
