Hello there Johann! I think you've made a great choice with neko. It's a very lightweight vm, very easy to grasp and understand how it works!
> If someone could answers my questions, I would greatly appreciate :) > - license : are there plans to change the license ? to something more > 'free', public domain or give the copyright to a foundation ? it's not that > I don't like the GPL license but I still have a very bad experience with > OpenSolaris which has suddenly change license to something private (thanks > oracle again). I guess you can understand I have a few fears about GPL, it's > not a full proof guarantee for the futur. > Well, I can't help you with that. But public domain could suffer from a sudden change to something private as well. Or maybe I'm missing the point. > - NekoVM : is there a basic IO support in nekoVM, at least to read and > write files ? so I could build a parser Eria -> Neko with it ? > Yes! You should as Justin said check out how haxe standard libs were made with neko. They all use the neko standard library ( you can see the neko standard libs' source code here: http://code.google.com/p/nekovm/source/browse/#svn%2Ftrunk%2Flibs ), and build up an oop structure with haxe. But OOP isn't the only paradigm you can build with neko, of course. Neko compiler itself was bootstrapped using nekoml, an ml-based language, with pattern matching, etc. > - NekoVM : some archive support ? zip, tar, gz, anything ? > Yes. On the std libs you'll find zlib bindings, and as Justin said, there's also the hxformat library, with tons of file formats. You could compile them as a separate .n file and dynamically load them at runtime by your language. > - NekoVM : my language requieres to have some advance reflexion, I want to > store constraint informations on a function arguments, x between 0 and 10 . > I'm not sure I follow you here. Can't you ensure the constraints by asserting the values at the beginning of your function block? Anyway neko is a dynamically typed vm, so it's naturally very reflection-oriented. > - NekoVM : how are objects organize ? in parrot I could store > primitives/class/functions in namespaces and acces them using reflexion. Is > there something similar in NekoVM. something like paths or namespaces ? > So, a little like javascript, neko is a language oriented by a few primitives: object, array, function, string, int, double and abstract (boxed c) types. Objects are like relational arrays with very fast field lookup. You can emulate namespaces by having nested objects: my.long.package.Class would be actually something like { my: { long: {package: { Class:(class contents...) } } } } Also like Javascript, neko is a prototype-based vm, so you can achieve inheritance by stacking prototype objects. Cheers! Cauê
-- Neko : One VM to run them all (http://nekovm.org)
