Nicolas,
I have read the Neko language specs. and what I want to know is
this... what would be involved for me to be able to compile neko code
into a running image in the same way that I can do with Smalltalk or
LISP for example.
Presumably the code generation part of nekoc would need to be glued
together with the vm or something along those lines ie to be able to
parse text, generate ast's etc and then generate actual VM byte codes
from that assuming no errors along the way. All of this exists in
some form or other but in two parts: nekoc and neko. If nekoc was
written in neko (is it???) then this would make it easier!
My goal would be able to either write a library/extension (preferred)
or have to extend the code base (a fork!, not preferred!!) so that I
can then write self-modifying code. Once I had that ability then I
would be on the way to writing my LISP system in Neko.
So, what are your thoughts on this... I am reasonably serious about
doing this but I have about 14 hours of Neko experience in total and
ZERO exposure to the actual source code so far. I am just trying to
get a feel for what would be involved to be able to do this.
Of course, it may do this already and I just didn't see it, it's
10:30pm and I have been up for 17 hours today and a full days seminar
tomorrow!
:-)
Sigh, so much to hack so little time to do it!
Sean Charles
--
Neko : One VM to run them all
(http://nekovm.org)
