Hello Konstatin,
I have ported more or less everything which is necessary to interpret
the byte code (others.c, interp.c, alloc.c, callback.c). It compiles,
but I can't test without real byte code - so currently I am working
(more thinking) about loader.c.
If nimrod code runs on the bare metal I can't say, but I guess yes,
because it is self contained (the compiler and the essential libraries
are written in nimrod) and it translates to pure C.
If I am step further with loader.c I can put the sources on github.
Cheers, Adrian.
Am 14.07.2012 15:44, schrieb Konstantin Tcholokachvili:
Hello Adrian,
Does nimrod can be run on a bare metal? I mean compile it as a kernel?
And how much are you advanced on your port? Are the sources somewhere?
Thanks in advance,
Konstantin Tcholokachvili
2012/7/13 Adrian Veith <[email protected]
<mailto:[email protected]>>
Hi,
I am currently working to port the neko VM to the nimrod language.
At the first look this seems to be ridiculous, but my idea is to
have a neko VM with a precise garbage collector and implemented in
a modern and efficient language. If this turns out successful, I
have more in mind with Haxe, neko and nimrod.
Currently I have translated the main interpreter loop and now I am
working on the loader, which has to be redesigned because nimrod
is much more strict than C (because of the precise garbage
collector, I can't do some tricks used currently in neko). Since
nimrod looks very much like Python mixed with Pascal and Lisp,
this might be interesting for you.
Cheers, Adrian.
Am 13.07.2012 17:19, schrieb Konstantin Tcholokachvili:
Hello,
I'm planning to write a hobby OS.
I already hacked a little kernel which needs to be rewritten.
The idea is to be able to write most parts in my preferred
languages such as Python and Mythryl.
The core (memory allocation, etc) will be in C and asm.
I started Python to neko and Mythryl to neko projects but they
aren't yet complete.
So, NekoVM is the cooler VM I found, I plan to integrate it in
the kernel level, but one thing makes me wonder: is the use of GC
really mandatory? Or this is just to avoid memory allocation
related errors?
Because instead to port NekoVM + GC, for me it would be much
easier to make a neko compatible interpreter, say in flex & bison.
Thus reducing the size of the binary.
As you are experienced with NekoVM, what's your opinion?
Best regards,
Konstantin Tcholokachvili
This body part will be downloaded on demand.
--
Neko : One VM to run them all
(http://nekovm.org)
This body part will be downloaded on demand.
--
Neko : One VM to run them all
(http://nekovm.org)
